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

From Merlin Moncure
Subject Re: hstore ==> and deprecate =>
Date
Msg-id AANLkTimYBykhwjYx0ne4wKpGWuqxzxGCPf8NESxGo9HI@mail.gmail.com
Whole thread Raw
In response to Re: hstore ==> and deprecate =>  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Jun 11, 2010 at 5:23 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Joseph Adams <joeyadams3.14159@gmail.com> writes:
>> To repeat an earlier question (which was in turn repeating an earlier
>> question), would it be possible to do one of these, yielding '
>> "key"=>"this", "key2"=>"that" '::hstore  :
>
>> 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:
>
> contrib_regression=# select hstore(row('this', 'that'));
>           hstore
> ----------------------------
>  "f1"=>"this", "f2"=>"that"
> (1 row)
>
> and the only thing lacking is an easy way to specify the column names
> associated with the anonymous record type.  Extending the ROW()
> construct with AS labels as suggested above might be a reasonable way.

+1

A couple of people were just requesting that very thing (ROW/AS) on
the IRC channel today.  row() is a pretty useful mechanism and it
would be nice to have it more defensible vs. table changes.

merlin


pgsql-hackers by date:

Previous
From: Florian Pflug
Date:
Subject: Re: Proposal for 9.1: WAL streaming from WAL buffers
Next
From: Josh Berkus
Date:
Subject: Re: Proposal for 9.1: WAL streaming from WAL buffers