From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Differentiate Between Zero-Length String and NULL Column Values |
Date: | 2007-01-30 13:13:34 |
Message-ID: | 20070130131334.GD31676@phlogiston.dyndns.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Tue, Jan 30, 2007 at 04:32:22PM +1100, Phillip Smith wrote:
> SHAMPOO","EQUEST","401600","0.00","0.00","0.00","0.00","10.00",""
^^
> SELECT * FROM tmpstk WHERE ean = NULL;
^^^^
Along with what Michael Fuhr said in his post about equality and
NULL, Postgres doesn't treat the empty string and NULL as equivalent
(because they're not). Only Oracle has that dodgy interpretation of
SQL, as far as I know. If you want to use the empty string, you need
WHERE ean = ''
If you want instead ean to be NULL, use the traditional \N to signify
NULL on your way in, or define null some other way.
A
--
Andrew Sullivan | ajs(at)crankycanuck(dot)ca
Users never remark, "Wow, this software may be buggy and hard
to use, but at least there is a lot of code underneath."
--Damien Katz
From | Date | Subject | |
---|---|---|---|
Next Message | Bart Degryse | 2007-01-30 13:38:07 | Re: Differentiate Between Zero-Length String and NULLColumn Values |
Previous Message | Niklas Bergius | 2007-01-30 10:40:39 | Arrays, multidimensional ANY (v 8.2) |