Re: Name column

Поиск
Список
Период
Сортировка
От André Fernandes
Тема Re: Name column
Дата
Msg-id COL112-W51A7BE943DBAF39892D2058A620@phx.gbl
обсуждение исходный текст
Ответ на Re: Name column  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: Name column  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Name column  (Pavel Stehule <pavel.stehule@gmail.com>)
Список pgsql-hackers
<br /><br />> Date: Fri, 24 Sep 2010 08:01:35 -0400<br />> Subject: Re: [HACKERS] Name column<br />> From:
robertmhaas@gmail.com<br/>> To: heikki.linnakangas@enterprisedb.com<br />> CC: arhipov@dc.baikal.ru;
pgsql-hackers@postgresql.org<br/>> <br />> On Fri, Sep 24, 2010 at 6:35 AM, Heikki Linnakangas<br />>
<heikki.linnakangas@enterprisedb.com>wrote:<br />> > For historical reasons PostgreSQL supports calling a
functionwith a single<br />> > argument like "column.function", in addition to "function(column)". There is<br
/>>> a function "name(text)" that casts the input to the 'name' datatype, so your<br />> > example casts
therow to text and from text to name.<br />> <br />> I'm starting to wonder if we should think about deprecating
this<br/>> behavior. It is awfully confusing and unintuitive.<br />> <br /><br />I agree, it is very unintuitive.
<br/>+1  for deprecating this behavior.<br /> 

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: git cherry-pick timestamping issue
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Configuring synchronous replication