Re: IN clause - Mailing list pgsql-general

From Brandon Aiken
Subject Re: IN clause
Date
Msg-id F8E84F0F56445B4CB39E019EF67DACBA3C4BFA@exchsrvr.winemantech.com
Whole thread Raw
In response to Re: IN clause  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: IN clause  (Marcus Engene <mengpg@engene.se>)
List pgsql-general
Hasn't it been said enough?  Don't allow NULLs in your database.
Databases are for storing data, not a lack of it.  The only time NULL
should appear is during outer joins.

--
Brandon Aiken
CS/IT Systems Engineer
-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org] On Behalf Of Martijn van
Oosterhout
Sent: Friday, November 24, 2006 7:20 AM
To: surabhi.ahuja
Cc: A. Kretschmer; pgsql-general@postgresql.org
Subject: Re: [GENERAL] IN clause

On Fri, Nov 24, 2006 at 05:31:07PM +0530, surabhi.ahuja wrote:
> That is fine
> but what I was actually expecting is this
> if
> select * from table where col_name in (null, 'a', 'b');
>
> to return those rows where col_name is null or if it = a or if it is =
b
>
> But i think in does not not support null queries , am i right?

You'll need to check the standard, but IN() treats NULL specially, I
think it returns NULL if any of the elements is null, or something like
that. It certainly doesn't work the way you think it does.

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability
to litigate.

pgsql-general by date:

Previous
From: "William Leite Araújo"
Date:
Subject: Re: How to clone a table so that primay and foreign keys remain
Next
From: Marcus Engene
Date:
Subject: Re: IN clause