| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org, Dmitriy Igrishin <dmitigr(at)gmail(dot)com>, Jan Urbański <wulczer(at)wulczer(dot)org> |
| Subject: | Re: hstores in pl/python |
| Date: | 2010-12-14 17:14:45 |
| Message-ID: | 4D07A605.4090300@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/14/2010 12:06 PM, Robert Haas wrote:
>> I haven't actually figured out what the benefit would be, other than
>> buzzword compliance and a chance to invent some random nonstandard
>> syntax. If the element values all have to be the same type, you've
>> basically got hstore.
> Not exactly, because in hstore all the element values have to be,
> specifically, text. Having hstores of other kinds of objects would,
> presumably, be useful.
>
I love hstore, and I've used it a lot, but I don't think there's much
future in doing this. This is part of what JSON would buy us, isn't it?
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2010-12-14 17:17:39 | Re: Complier warnings on mingw gcc 4.5.0 |
| Previous Message | Tom Lane | 2010-12-14 17:12:43 | Re: hstores in pl/python |