Bruce Momjian <[EMAIL PROTECTED]> writes:
> I am a little uncomfortable about this. It means that CREATE TABLE will
> create a table in 'public' if the user doesn't have a schema of their
> own, and in their private schema if it exists. I seems strange to have
> such a distinction based on whether a private schema exists. Is this OK?
You have a better idea?
Given that we want to support both backwards-compatible and SQL-spec-
compatible behavior, I think some such ugliness is inevitable.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
