Re: hstores in pl/python

From: Andres Freund <andres(at)anarazel(dot)de>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: 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-13 15:13:24
Message-ID: 201012131613.25576.andres@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Monday 13 December 2010 16:01:35 Pavel Stehule wrote:
> 2010/12/13 Andres Freund <andres(at)anarazel(dot)de>:
> > 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?
>
> name and interface - hstore is designed as external module - a
> internal class can be designed different.
Could you actually name such a difference rather than pointing to some airily
hint of one? That would make it way much easier to see where you want to go.

Andres

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-12-13 15:14:29 Re: GiST insert algorithm rewrite
Previous Message Pavel Stehule 2010-12-13 15:13:09 Re: hstores in pl/python