Re: What's the CURRENT schema ?

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "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-04 21:49:56
Message-ID: EKEJJICOHDIEMGPNIFIJMEBKHGAA.Inoue@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
>
> Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> writes:
> > I see. However my main problem is that the schema of unqualified
> > vs1 is affected by the existence of yamada.vs1. I don't think
> > it's a useful behavior.
>
> Well, if you don't like it, you could set the search_path to be just
> public,

Yes I don't like it and probably I would do it for myself but
I couldn't force other people to do so. Well for example,
how could psqlodbc driver know the CURRENT schema ?

> or public and then the user's personal namespace.

The order isn't the problem at all. Would the *public*
be the CURRENT schema then ? If I recognize correctly,
neither is the CURRENT schema in the current spec.

regards,
Hiroshi Inoue

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-04-04 22:33:27 Re: timeout implementation issues
Previous Message Bruce Momjian 2002-04-04 21:18:01 Re: timeout implementation issues