| From: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: IN and ANY |
| Date: | 2004-03-02 20:44:38 |
| Message-ID: | Pine.LNX.4.44.0403022138160.13979-100000@zigo.dhs.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2 Mar 2004, Joe Conway wrote:
> regression=# select 1 where array[1] in (array[1]);
> ?column?
> ----------
> 1
> (1 row)
>
> regression=# select 1 where array[1] in (array[1,2]);
> ?column?
> ----------
> (0 rows)
The only reason I brought it up was that to me ANY and IN are pretty much
the same kind of operator. Up until now I thought that IN really was the
same as =ANY, but it isn't. I don't like that but of course I have to
accept it. I would rather have had some elem function/operator for arrays
like:
1 ELEM IN array[1,2]
or
1 = ANY ELEM arra[1,2]
But as usual I'm 6 months late with my objections :-)
--
/Dennis Björklund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2004-03-02 21:42:03 | Re: IN and ANY |
| Previous Message | Bruce Momjian | 2004-03-02 20:08:22 | Re: simple make check failures |