Dave Page wrote:
Erwin Brandstetter wrote:
In a future release we could default to database "postgres" for global
objects, which is there for purposes like this one, isn't it?
It would be convenient to to open the SQL window directly from a role.
As long as we work on global objects like roles, the database does not
make a difference.
Of course, database "postgres" could be absent (pg versions < 7.4 or
dropped for some reason). We could further default to template1, but I
would rather warn the user that database "postgres" is missing and not
open the SQL window. We want to avoid trash in the template. And there
might be some potential for users to overlook what database they are
connected to, even if it is displayed clearly enough.
Still, I would definitely like the feature.
It would have to be the maintenance DB, but I'm not convinced that would
be overly obvious to the user. Conversely I'm not convinced it wouldn't
either now we have the database selector on the query tool, so if you
want to work up a patch...
/D
Of course, the maintenance DB!
I am afraid you won't be seeing C++ patches from me any time soon. But
who can tell the future?
Regards
Erwin
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
