From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Fernando Nasser <fnasser(at)redhat(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: What's the CURRENT schema ? |
Date: | 2002-04-10 09:41:22 |
Message-ID: | 3CB408C2.8C8E6128@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Fernando Nasser wrote:
>
> As most things in the SQL standard, you have to collect information
> from several places and add it together.
>
> Look at 4.20, 11.1 and specially at the rules for
> <schema qualified name>.
>
> Then think a little bit about scenarios, trying to apply the rules.
>
> It is a pain, but there is no other way.
I couldn't find the description CURRENT_SCHEMA == CURRENT_USER.
If I recognize SQL99 correctly, the CURRENT schema is the schema
defined in a <SQL-client module> not restricted to the CURRENT
user.
Well here's my proposal.
1) Use the different search path for table name and
others.
2) Allow only one schema other than temp or catalog in
the table name search path so that we can call it
the CURRENT schema.
Comments ?
regards,
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2002-04-10 10:39:06 | Re: RFC: Restructuring pg_aggregate |
Previous Message | Thomas Lockhart | 2002-04-10 06:22:14 | Re: timeout implementation issues |