Re: why table.name is translated to (name.*)::name?

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Ian Barwick <barwick(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: why table.name is translated to (name.*)::name?
Date: 2010-03-30 14:38:41
Message-ID: 162867791003300738u788f74e9w7bcd5e884f93eeaa@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2010/3/30 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Ian Barwick <barwick(at)gmail(dot)com> writes:
>> 2010/3/30 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:
>>> we can use a non existing column "name". What does mean?
>
>> FYI this has caused me (and presumably a few other people) a bit of
>> head-scratching, e.g.:
>>   http://archives.postgresql.org/pgsql-general/2010-03/msg00362.php
>
> We could make that stop happening if we were willing to restrict the
> cases in which an I/O conversion would be applied, but I think the cure
> might be worse than the disease.  It would be an entirely arbitrary
> restriction of a feature.
>

it is confusing :(. It returns some data, but it have to returns syntax error.

Regards
Pavel Stehule

>                        regards, tom lane
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 2010-03-30 15:22:07 Re: Problems with variable cursorname in ecpg
Previous Message Tom Lane 2010-03-30 14:16:43 Re: why table.name is translated to (name.*)::name?