From: | Don Baccus <dhogaza(at)pacifier(dot)com> |
---|---|
To: | Pete Forman <pete(dot)forman(at)westgeo(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Question about Oracle compatibility |
Date: | 2000-11-28 14:44:21 |
Message-ID: | 3.0.1.32.20001128064421.017e34b0@mail.pacifier.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At 09:59 AM 11/28/00 +0000, Pete Forman wrote:
>Mario Weilguni writes:
> > This gets really bad when the actual data is coming from a
> > webinterface, I've to handle 2 different queries for the case empty
> > string and non-empty string.
>
>In their documentation both Oracle 7 and 8 state:
>
> Oracle currently treats a character value with a length of zero
> as null. However, this may not continue to be true in future
> releases, and Oracle recommends that you do not treat empty
> strings the same as NULLs.
Yeah, but this is harder than it sounds! NULL and '' are indistinguishable
in queries, so how do you treat them differently? Has to be in the
application code, I guess.
- Don Baccus, Portland OR <dhogaza(at)pacifier(dot)com>
Nature photos, on-line guides, Pacific Northwest
Rare Bird Alert Service and other goodies at
http://donb.photo.net.
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 2000-11-28 14:48:21 | Re: [HACKERS] is it a bug? |
Previous Message | Don Baccus | 2000-11-28 14:41:53 | RE: Full text Indexing -out of contrib and into main.. |