Re: hstore ==> and deprecate => - Mailing list pgsql-hackers

From Tom Lane
Subject Re: hstore ==> and deprecate =>
Date
Msg-id 28224.1276362062@sss.pgh.pa.us
Whole thread Raw
In response to Re: hstore ==> and deprecate =>  ("David E. Wheeler" <david@kineticode.com>)
List pgsql-hackers
"David E. Wheeler" <david@kineticode.com> writes:
> On Jun 11, 2010, at 2:23 PM, Tom Lane wrote:
>>> hstore(key := 'this', key2 := 'that')
>>> hstore(key => 'this', key2 => 'that')
>>> hstore(row('this' AS key, 'that' AS key2))
>> 
>> The last of those is probably the easiest to get to.  We already have
>> hstore_from_record:

> Is not the first one simply a function with any number of named params?

No, because the desire presumably would be to be able to use any set of
parameter names with that one function ... which absolutely flies in the
face of our current notion of what a parameter name means.  You'd
essentially have to disable the ability to have function overloading.
(Which probably means it Ain't Happening.)
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Idea for getting rid of VACUUM FREEZE on cold pages
Next
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade output directory