| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | David E(dot) Wheeler <david(at)kineticode(dot)com> |
| Cc: | 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:08:06 |
| Message-ID: | 1289505981-sup-5481@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from David E. Wheeler's message of jue nov 11 15:45:55 -0300 2010:
> On Nov 11, 2010, at 10:19 AM, Darren Duncan wrote:
>
> > I think that it would be best to implement MULTISET in the same way that a TABLE is implemented. Logically and structurally they are the same thing, but that a MULTISET typically is used as a field value of a table row. Aka, a table and a multiset are just different names for a relation, loosely speaking.
>
> 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)
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2010-11-11 20:15:54 | Re: renaming contrib. (was multi-platform, multi-locale regression tests) |
| Previous Message | Tom Lane | 2010-11-11 19:13:24 | Re: wCTE behaviour |