Date: Fri, 24 Sep 2010 08:01:35 -0400
Subject: Re: [HACKERS] Name column
From: [email protected]
To: [email protected]
CC: [email protected]; [email protected]
On Fri, Sep 24, 2010 at 6:35 AM, Heikki Linnakangas
wrote:
behavior. It is awfully confusing and unintuitive.
Subject: Re: [HACKERS] Name column
From: [email protected]
To: [email protected]
CC: [email protected]; [email protected]
On Fri, Sep 24, 2010 at 6:35 AM, Heikki Linnakangas
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 thisargument 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.
behavior. It is awfully confusing and unintuitive.
+1 for deprecating this behavior.