Horton

Re: multiset patch review

Itagaki Takahiro <itagaki.takahiro@gmail.com>

View thread
From: Itagaki Takahiro <itagaki.takahiro@gmail.com>
To: Dimitri Fontaine <dimitri@2ndquadrant.fr>
Cc: Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Pavel Stehule <pavel.stehule@gmail.com>, Alvaro Herrera <alvherre@commandprompt.com>
Date: 2011-02-05T02:11:22Z
Lists: pgsql-hackers 
On Sat, Feb 5, 2011 at 04:24, Dimitri Fontaine <dimitri@2ndquadrant.fr> wrote:
>> In math class, maybe.  But in programming, no.  Multiset is a
>> datatype.  Array is a different datatype.  There is no reason why we
>> need to clutter our parser with extra keywords to support a
>> non-standard feature extension.
>
> My understanding is that we will have to have those functions defined
> and user visible, and that we benefit from function overloading which is
> not in the standard.  So there's no reason not to provide those function
> for arrays already, then extend to full multiset support.
>
> Given PostgreSQL overloading, yes, arrays are multisets as far as
> defining those standard compliant APIs is concerned.  AFAIUI.

Yes, I'd like to use overloading.
Choosing arbitrary names increases learning costs for users.

-- 
Itagaki Takahiro