From: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com> |
---|---|
To: | Darren Duncan <darren(at)darrenduncan(dot)net> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: MULTISET and additional functions for ARRAY |
Date: | 2010-11-12 01:36:34 |
Message-ID: | AANLkTinnNLphOXPxOJYGU93ThyCHOu4iZHqx7Pycn3sp@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Nov 12, 2010 at 06:06, Darren Duncan <darren(at)darrenduncan(dot)net> wrote:
> This is one place that SQL made things more complicated than they needed to
> be. Multisets have generally the same structure *and* operators (union,
> etc) as tables, but they use different syntax for each. A better design
> would be to make tables and multisets interchangeable. Its an unnecessary
> distinction.
We can use unnest() to convert MULTISET into TABLE, and collect() agg
function from TABLE to MULTISET. I don't think they need to have the
same on-disk structure; they can share operators and constructor syntax
even now.
--
Itagaki Takahiro
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2010-11-12 01:54:17 | Re: duplicate connection failure messages |
Previous Message | Tatsuo Ishii | 2010-11-12 01:29:08 | Re: Delimited identifier brhavior |