| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| 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:18:41 |
| Message-ID: | AANLkTi=VCRsP3E_3h8p535qStQm0j7ViQMMtBgOzSyrY@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2010/12/14 Andrew Dunstan <andrew(at)dunslane(dot)net>:
> 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?
Well, JSON would give you numbers and booleans, but that's a pretty
small subset of all the types in the universe. I think the main thing
JSON would give you is hierarchical structure.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-12-14 17:21:12 | Re: hstores in pl/python |
| Previous Message | Pavel Stehule | 2010-12-14 17:18:21 | Re: hstores in pl/python |