| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Darren Duncan <darren(at)darrenduncan(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: MULTISET and additional functions for ARRAY |
| Date: | 2010-11-11 20:46:42 |
| Message-ID: | AANLkTinRhhwPUuJNHWA=srq1NumQVVKTPqz8TATe0Xbu@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 11, 2010 at 3:42 PM, David E. Wheeler <david(at)kineticode(dot)com> wrote:
> On Nov 11, 2010, at 12:08 PM, Alvaro Herrera wrote:
>
>>> That sounds like a composite type to me.
>>
>> No, it's "perpendicular" in the sense that while a composite type allows
>> you to have different columns, this multiset thing lets you have "rows"
>> (I initially thought about them as sets of scalars, but AFAIU they could
>> in turn be rows)
>
> How is that different from an array of RECORDs?
not a whole lot outside of syntax details...there is a decent summary
here: http://waelchatila.com/2005/05/18/1116485743467.html
I like this part: "Alternatively the SQL standard also permits the
same construct with the bracket trigraphs ??( and ??)" :-D
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Darren Duncan | 2010-11-11 21:06:32 | Re: MULTISET and additional functions for ARRAY |
| Previous Message | David E. Wheeler | 2010-11-11 20:42:59 | Re: MULTISET and additional functions for ARRAY |