| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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:21:12 |
| Message-ID: | AANLkTinVMVC9hzZwZpUmrNdYGyz-Hb=8xm-pipja12Oa@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2010/12/14 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Tue, Dec 14, 2010 at 11:51 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> 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.
>
> Maybe, but I'm sure they'd have far less application than hstore.
> There's a reason why that's based on text and not some other type ...
Sure. You can smash anything to a string, and it's often a very
practical way to go, though not always.
I am not necessarily expressing any interest in building such a
facility, just pointing one way that it might hypothetically have an
advantage over hstore. Whether it's worth pursuing is another
question.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Bartunov | 2010-12-14 17:21:57 | Re: hstores in pl/python |
| Previous Message | Robert Haas | 2010-12-14 17:18:41 | Re: hstores in pl/python |