From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Dmitriy Igrishin <dmitigr(at)gmail(dot)com>, Jan Urbański <wulczer(at)wulczer(dot)org> |
Subject: | Re: hstores in pl/python |
Date: | 2010-12-13 14:51:14 |
Message-ID: | 201012131551.14772.andres@anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Monday 13 December 2010 15:27:48 Pavel Stehule wrote:
> 2010/12/13 Dmitriy Igrishin <dmitigr(at)gmail(dot)com>:
> > Hey Pavel,
> >
> > 2010/12/13 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> >
> >> Hello
> >>
> >> this is little bit offtopic, sorry.
> >>
> >> I am thinking, so we need a standard associative array support in core
> >> - like Perl, Python or Javascript. So, I don't think, so migration of
> >> hstore to core is good idea.
> >
> > Could you tell why in-core associative array support would be better
> > than in-core hstore support ?
> > We enjoying to use hstore and thinking that it is implemented great.
>
> Because hstore is PostgreSQL specific type. More well known syntax is
> better. More - who know, what is hstore? But everybody know, what is
> associative array or hash.
So youre disturbed by the name?
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2010-12-13 14:55:04 | Re: ALTER EXTENSION ... UPGRADE; |
Previous Message | Alexey Klyukin | 2010-12-13 14:42:51 | Re: Optimize PL/Perl function argument passing [PATCH] |