From: | Yaroslav Tykhiy <yar(at)barnet(dot)com(dot)au> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Schema search path |
Date: | 2010-09-14 00:21:30 |
Message-ID: | EE1418DB-4004-4334-8D56-93ACD014F624@barnet.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 14/09/2010, at 8:56 AM, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>> Yaroslav Tykhiy wrote:
>>> SELECT * FROM foo.bar WHERE bar.a=1;
>>> ^^^ this means foo.bar
>
>>> Do you think it's a feature or a bug? :-)
>
>> Feature, and SQL-standard behavior.
>
> It might be worth pointing out that this has nothing to do with
> search_path; rather, the key is that the FROM clause establishes
> a table alias "bar" for the query.
Sure, that makes sense because it just extends the well-known aliasing
for unqualified column names, as in "SELECT a FROM foo", to table
names as well. But a remark on this feature in the SCHEMA related
documentation pages can be a good idea IMHO.
Thanks!
Yar
From | Date | Subject | |
---|---|---|---|
Next Message | Yaroslav Tykhiy | 2010-09-14 00:37:27 | Re: Query plan choice issue |
Previous Message | Tom Lane | 2010-09-13 22:56:04 | Re: Schema search path |