Hi Ben,

This was indeed a bug, and I just checked in a fix for it on the trunk. I've also attached a patch file to this response in case you are building from 10.1 sources and want to include this fix. If not, then you'll have to rename your .sql file to change the name until 10.2 is released.

I agree that it would be nice to have a programmatic name vs user-displayed name for query definitions. The core query architecture doesn't allow for that currently, but it would be a relatively simply addition if you'd like to add that to your feature list for 10.2. Talk with Mark about getting this on the list and prioritized.

So for now, a query has a name, and that name is used both in queries that reference it and in the user interface.