Re: Some array semantics issues - Mailing list pgsql-hackers

From David Fetter
Subject Re: Some array semantics issues
Date
Msg-id 20051116210805.GA22353@fetter.org
Whole thread Raw
In response to Re: Some array semantics issues  (Greg Stark <gsstark@mit.edu>)
Responses Re: Some array semantics issues  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Nov 16, 2005 at 03:03:53PM -0500, Greg Stark wrote:
> 
> Tom Lane <tgl@sss.pgh.pa.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@fetter.org http://fetter.org/
phone: +1 510 893 6100   mobile: +1 415 235 3778

Remember to vote!


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Some array semantics issues
Next
From: Tom Lane
Date:
Subject: Re: Some array semantics issues