From: | "Vincent Hikida" <vhikida(at)inreach(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Nulls get converted to 0 problem |
Date: | 2003-06-04 20:54:26 |
Message-ID: | 024d01c32adb$7c1d3840$6601a8c0@HOMEOFFICE |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks for the detail. :)
Vincent Hikida,
Member of Technical Staff - Urbana Software, Inc.
"A Personalized Learning Experience"
----- Original Message -----
From: "scott.marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: "Vincent Hikida" <vhikida(at)inreach(dot)com>
Cc: "Avi Schwartz" <avi(at)CFFtechnologies(dot)com>; <pgsql-general(at)postgresql(dot)org>
Sent: Wednesday, June 04, 2003 1:28 PM
Subject: Re: [GENERAL] Nulls get converted to 0 problem
> On Wed, 4 Jun 2003, Vincent Hikida wrote:
>
> > > FYI, "" does NOT equal NULL does not equal 0.
> >
> >
> > Interesting, I noticed that a few days ago. I noticed that in pg sql, if
I
> > used RTRIM on a column with all blanks. the RTRIM'ed result is not null.
In
> > Oracle I think it would be a null. That is in Oracle "" and NULL are
> > equivalent.
>
> Yeah, this is an issue we run into a lot on the lists. Basically, Oracle
> got this one wrong, people wrote a lot of code expecting it, and now
> Oracle can't change it to the proper behaviour without breaking folks'
> applications.
>
> There is a setting in postgresql that turns where field=NULL into where
> field IS NULL, but I don't think there's much more support for "" being
> equivalent to NULL.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | scott.marlowe | 2003-06-04 20:55:29 | Re: Nulls get converted to 0 problem |
Previous Message | Bruce Momjian | 2003-06-04 20:31:02 | Re: libpgeasy.h and 7.3.2 |