Re: hstore ==> and deprecate =>
От | Merlin Moncure |
---|---|
Тема | Re: hstore ==> and deprecate => |
Дата | |
Msg-id | AANLkTimYBykhwjYx0ne4wKpGWuqxzxGCPf8NESxGo9HI@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: hstore ==> and deprecate => (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | 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 по дате отправления: