Skip site navigation (1) Skip section navigation (2)

Re: Name column

From: =?iso-8859-1?B?QW5kcukgRmVybmFuZGVz?=<andre(dot)de(dot)camargo(dot)fernandes(at)hotmail(dot)com>
To: <robertmhaas(at)gmail(dot)com>, <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: <arhipov(at)dc(dot)baikal(dot)ru>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Name column
Date: 2010-09-24 15:29:42
Message-ID: COL112-W51A7BE943DBAF39892D2058A620@phx.gbl (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

> Date: Fri, 24 Sep 2010 08:01:35 -0400
> Subject: Re: [HACKERS] Name column
> From: robertmhaas(at)gmail(dot)com
> To: heikki(dot)linnakangas(at)enterprisedb(dot)com
> CC: arhipov(at)dc(dot)baikal(dot)ru; pgsql-hackers(at)postgresql(dot)org
> 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.

I agree, it is very unintuitive. 
+1  for deprecating this behavior.

In response to


pgsql-hackers by date

Next:From: Robert HaasDate: 2010-09-24 15:29:55
Subject: Re: Configuring synchronous replication
Previous:From: Tom LaneDate: 2010-09-24 15:23:10
Subject: Re: git cherry-pick timestamping issue

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group