From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
Cc: | "Fernando Nasser" <fnasser(at)redhat(dot)com>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: What's the CURRENT schema ? |
Date: | 2002-04-08 17:41:31 |
Message-ID: | 21924.1018287691@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> writes:
> However I can see the following at 5.4 Names and Identifiers
> 11) If a <schema qualified name> does not contain a <schema name>, then
> Case:
> a) If the <schema qualified name> is contained in a <schema
> definition>,
> then the <schema name> that is specified or implicit in the <schema
> definition>
> is implicit.
Yes. Fernando, our existing CREATE SCHEMA command does not get this
right for references from views to tables, does it? It seems to me that
to get compliant behavior, we'll need to temporarily push the new schema
onto the front of the namespace search path while parsing view
definitions inside CREATE SCHEMA.
(The relevance to the current discussion is that this is easy to do if
SET variables roll back on error ... but it might be tricky if they do
not.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2002-04-08 17:56:08 | Re: timeout implementation issues |
Previous Message | Tom Lane | 2002-04-08 17:20:21 | Re: timeout implementation issues |