Re: [HACKERS] default namespace (schema) confusion

2002-10-17 Thread Bruce Momjian
Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > I dislike double-testing the username in schema areas but not other > > places. Seems if we do it, we should do it consistently for all > > username references, or not at all. > > What other places do we have an explicit dependence o

Re: [HACKERS] default namespace (schema) confusion

2002-10-17 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> writes: > I dislike double-testing the username in schema areas but not other > places. Seems if we do it, we should do it consistently for all > username references, or not at all. What other places do we have an explicit dependence on the username?

Re: [HACKERS] default namespace (schema) confusion

2002-10-17 Thread Bruce Momjian
Tom Lane wrote: > Carl Anderson <[EMAIL PROTECTED]> writes: > > this use of "@" in the default schema is a bit counter intuitive > > so I offer the following patch against CVS > > Hmm, this seems like a wart, but then the db_user_namespace feature > is an acknowledged wart already. > > I think I'

Re: [HACKERS] default namespace (schema) confusion

2002-10-17 Thread Tom Lane
Carl Anderson <[EMAIL PROTECTED]> writes: > this use of "@" in the default schema is a bit counter intuitive > so I offer the following patch against CVS Hmm, this seems like a wart, but then the db_user_namespace feature is an acknowledged wart already. I think I'd be willing to hold still for t

[HACKERS] default namespace (schema) confusion

2002-10-17 Thread Carl Anderson
I have been looking forward to schemas (namespaces) for sometime. I had not been able to decipher the schema symantics necessary for a default schema, until I hacked the source a bit. Now I know that the rules to get a default schema using db_user_namespace = true search_path = '$user,public'