Re: What's the CURRENT schema ?

From: Fernando Nasser <fnasser(at)redhat(dot)com>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: What's the CURRENT schema ?
Date: 2002-04-05 16:39:55
Message-ID: 3CADD35B.176655C@redhat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Christopher Kings-Lynne wrote:
>
> > I really don't buy this argument; it seems exactly comparable to
> > arguing that the notion of current directory in Unix is evil, and
> > that users should be forced to specify absolute paths to every
> > file that they reference.
>
> You know, I'm kinda surprised that the spec doesn't define a CURRENT_SCHEMA
> variable you can query???
>

Maybe because it would be the same as CURRENT_USER.

For the standard, the schema name used (implied) to qualify objects
outside
a CREATE SCHEMA statement is a schema name with the SQL-session user id.
Except for functions and UDTs where each schema has a SQL-path for
searching those (the implied schema must always be in it though).
There must be an implementation-defined default for this SQL-path
(but the implied schema must also be in it).

--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser(at)redhat(dot)com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Clift 2002-04-05 16:48:08 Re: [Fwd: AW: UB-Tree's and patents]
Previous Message Tom Lane 2002-04-05 16:32:35 Re: PQescapeBytea is not multibyte aware