Re: why table.name is translated to (name.*)::name? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: why table.name is translated to (name.*)::name?
Date
Msg-id 16395.1269958603@sss.pgh.pa.us
Whole thread Raw
In response to Re: why table.name is translated to (name.*)::name?  (Ian Barwick <barwick@gmail.com>)
Responses Re: why table.name is translated to (name.*)::name?
List pgsql-hackers
Ian Barwick <barwick@gmail.com> writes:
> 2010/3/30 Pavel Stehule <pavel.stehule@gmail.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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Ian Barwick
Date:
Subject: Re: why table.name is translated to (name.*)::name?
Next
From: Pavel Stehule
Date:
Subject: Re: why table.name is translated to (name.*)::name?