From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fernando Nasser <fnasser@redhat.com>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-hackers@postgresql.org
Subject: Re: RFD: schemas and different kinds of Postgres objects
Date: Tue, 22 Jan 2002 16:34:47 -0500
Message-ID: <28787.1011735287@sss.pgh.pa.us> (raw)
In-Reply-To: <3C4DD909.F26FD0D1@redhat.com>
References: <Pine.LNX.4.30.0201211840260.687-100000@peter.localdomain>
<12239.1011661590@sss.pgh.pa.us>
<3C4D8A39.FF79CDC4@redhat.com>
<15339.1011716171@sss.pgh.pa.us>
<3C4D96C5.80BBF764@redhat.com>
<15638.1011718290@sss.pgh.pa.us>
<3C4DCBDB.689D7201@redhat.com>
<28199.1011732109@sss.pgh.pa.us>
<3C4DD34F.CC4D8B6@redhat.com>
<28557.1011734056@sss.pgh.pa.us>
<3C4DD909.F26FD0D1@redhat.com>
Fernando Nasser <fnasser@redhat.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, fnasser@redhat.com, peter_e@gmx.net
Subject: Re: RFD: schemas and different kinds of Postgres objects
In-Reply-To: <28787.1011735287@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox