From: | "Mel Jamero" <mel(at)gmanmi(dot)tv> |
---|---|
To: | <email(at)juergen-cappel(dot)de>, <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Retrieving NULL records |
Date: | 2003-07-29 11:20:38 |
Message-ID: | 000601c355c3$70a6a920$1b06a8c0@CMPMEL |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
it is now..
i had to port lots of our old C applications when i upgraded to a newer
postgres.
-----Original Message-----
From: pgsql-novice-owner(at)postgresql(dot)org
[mailto:pgsql-novice-owner(at)postgresql(dot)org]On Behalf Of
email(at)juergen-cappel(dot)de
Sent: Tuesday, July 29, 2003 2:40 PM
To: pgsql-novice(at)postgresql(dot)org
Subject: Re: [NOVICE] Retrieving NULL records
Shouldn't = NULL be considered a syntax error ?
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> schrieb am 29.07.2003, 07:41:15:
> "psql novice" writes:
> > stock=> select * from stock where qty = NULL;
>
> The correct incantation is
>
> select * from stock where qty IS NULL;
>
> Ordinary comparisons involving NULL always fail (or more accurately,
> return NULL). You have to use the special "is null" operator instead.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
From | Date | Subject | |
---|---|---|---|
Next Message | Nabil Sayegh | 2003-07-29 11:23:01 | Re: Retrieving NULL records |
Previous Message | Harry Broomhall | 2003-07-29 10:20:47 | Re: diff between two timestamps. |