| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Vlad Arkhipov <arhipov(at)dc(dot)baikal(dot)ru>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Name column |
| Date: | 2010-09-24 12:01:35 |
| Message-ID: | AANLkTim9nssn1MvDH0znHEDebnroS9yXRQYsZSqnDaBk@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 24, 2010 at 6:35 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> For historical reasons PostgreSQL supports calling a function with a single
> argument like "column.function", in addition to "function(column)". There is
> a function "name(text)" that casts the input to the 'name' datatype, so your
> example casts the row to text and from text to name.
I'm starting to wonder if we should think about deprecating this
behavior. It is awfully confusing and unintuitive.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-09-24 12:05:59 | Re: patch: SQL/MED(FDW) DDL |
| Previous Message | Robert Haas | 2010-09-24 11:58:36 | Re: pg_comments |