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

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: why table.name is translated to (name.*)::name?
Дата
Msg-id 162867791003300738u788f74e9w7bcd5e884f93eeaa@mail.gmail.com
обсуждение исходный текст
Ответ на Re: why table.name is translated to (name.*)::name?  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
2010/3/30 Tom Lane <tgl@sss.pgh.pa.us>:
> 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.
>

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

Regards
Pavel Stehule


>                        regards, tom lane
>


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: why table.name is translated to (name.*)::name?
Следующее
От: Dimitri Fontaine
Дата:
Сообщение: Re: GSoC