Re: Array comparison - subset

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Christopher Murtagh <christopher(dot)murtagh(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Array comparison - subset
Date: 2006-09-03 13:32:04
Message-ID: 20060903133204.GA67646@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Sep 03, 2006 at 12:59:08AM -0400, Tom Lane wrote:
> Michael Fuhr <mike(at)fuhr(dot)org> writes:
> > test=> SELECT ARRAY[1, 2, 3, 4] @ ARRAY[1, 3];
> > ?column?
> > ----------
> > t
> > (1 row)
>
> > In 8.2 the above example will work in the stock installation for
> > arrays of any type (i.e., with operands of type anyarray).
>
> [ blink... ] When did that get in, and why don't I see it in the
> documentation?

Looks like it arrived with the gin code.

http://archives.postgresql.org/pgsql-committers/2006-05/msg00007.php
http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_operator.h.diff?r1=1.142&r2=1.143

> The operand order seems exactly backward considering
> that all the pre-existing @ operators are "contained in", not
> "contains". Should we flip this around before it's too late?

I'd favor consistency, although I see that contrib/intarray has had
it backwards for a long time :-(

--
Michael Fuhr

In response to

Browse pgsql-general by date

  From Date Subject
Next Message mdean 2006-09-03 17:07:11 Re: [GENERAL] Thought provoking piece on NetBSD
Previous Message Ben Trewern 2006-09-03 10:54:06 pgFoundry.org not working!