From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Some array semantics issues |
Date: | 2005-11-16 21:08:05 |
Message-ID: | 20051116210805.GA22353@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Nov 16, 2005 at 03:03:53PM -0500, Greg Stark wrote:
>
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>
> > I could go for a separate operator that has the current behavior
> > (might as well ignore number of dimensions too, if we're going to
> > ignore bounds). Any thoughts about the operator name?
>
> Well to me these are two different cases. At least the way I see it
> {1,2} is a list of two numbers, and {{1,2,},{3,4}} is a list of two
> lists. They aren't the same and they don't even contain the same
> thing.
Right.
> It occurs to me that it would also make sense to have an operator
> that considered the arrays in an order-insensitive comparison.
That sounds more like the SQL:2003 MULTISET, which is essentially
unordered. Any plans for these?
Cheers,
D
--
David Fetter david(at)fetter(dot)org http://fetter.org/
phone: +1 510 893 6100 mobile: +1 415 235 3778
Remember to vote!
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-11-16 21:22:52 | Re: Some array semantics issues |
Previous Message | Tom Lane | 2005-11-16 21:03:15 | Re: Some array semantics issues |