2010/3/12 strk <s...@keybit.net>: > On Fri, Mar 12, 2010 at 10:47:45AM -0800, David Fetter wrote: >> On Fri, Mar 12, 2010 at 07:35:41PM +0100, Pavel Stehule wrote: >> > 2010/3/12 David Fetter <da...@fetter.org>: >> > > >> > > This is, by the way, an excellent argument for including hstore in >> > > core in 9.1. :) >> > >> > I like it - but it looking little bit strange - I thinking we need >> > only one function (maybe with some special support from pl executor) >> > >> > begin >> > update_field(NEW, 'field', value); >> > .... >> >> This doesn't seem like a terribly useful addition, it being specific >> to PL/pgsql. Then there's the quoting issue, which the above doesn't >> quite address. Putting hstore in would let all the other PLs use it, >> to the extent that they need such a thing. :) > > Plus pure SQL use ! > I was considering using hstore for a table value too for > a form of "historic table". Just to say I'd also be happy with > it being core in pgsql :) >
I see some disadvantages a) non intuitive name - hstore is very specific name b) effectivity (mainly inside trigger body) - plpgsql specific construct can be 10x faster. I would to see hash tables in core too, but I don't think so it is good solution for record updating. Regards Pavel > --strk; > > () Free GIS & Flash consultant/developer > /\ http://strk.keybit.net/services.html > -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers