From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Fernando Nasser <fnasser(at)redhat(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: RFD: schemas and different kinds of Postgres objects |
Date: | 2002-01-22 21:34:47 |
Message-ID: | 28787.1011735287@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Fernando Nasser <fnasser(at)redhat(dot)com> writes:
> In the historical mode: look into schema B (=> not found), look into
> ANY schema (finds it in A). Works as it is today.
No, it doesn't work the same as today, because in that implementation
both A and B can create the same tablename without complaint. It then
becomes very unclear which instance other people will get (unless your
"any" placeholder somehow implies a search order).
The idea of being able to put an "any" placeholder into the search list
is an interesting one, though. If we can resolve the ambiguity problem
it might be a useful feature.
I am a little troubled by the idea of placing "any" before the system
schema (what if JRandomLuser creates a table named "pg_class"?) but it
might be workable at the tail end of the path.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-01-22 21:47:27 | Re: TODO item question |
Previous Message | Fernando Nasser | 2002-01-22 21:26:33 | Re: RFD: schemas and different kinds of Postgres objects |