Re: fyi

From: maillist <maillist(at)tnss(dot)com>
To:
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: fyi
Date: 2003-08-01 06:16:39
Message-ID: 3F2A05C7.4C171687@tnss.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Stephan Szabo wrote:
>
> On Thu, 31 Jul 2003, maillist wrote:
>
> > select * from apps where (not apppag = null);
> > returns nothing when it should return every thing
>
> No. It should return nothing. apppag = null returns unknown for every
> row. Use IS NULL to test if a value is null.
hmmm now i'm confused when i set a value i don't use the phrase to null
and '= null' has always worked in the past, and if '= null' doesn't work
it should be an invalid query because i can see no other use for it, and
for the most part is, to are ignored anyways.

so would the correct query be
select * from apps where (not apppag = is null)
or
select * from apps where (not apppag is null)
both of these look silly, but I do use null in other fields on purpuse
to represent uninitailized fields. So I definitlay am going to have to
grep my code for "=*null" and check to see what needs to be done. Ijust
thought it was a bug, that should not have been found, because the query
had un needed checks. I need to do more testing before I allow
production servers to upgrade

Arno

In response to

  • Re: fyi at 2003-08-01 05:53:52 from Stephan Szabo

Responses

  • Re: fyi at 2003-08-01 06:30:36 from Stephan Szabo

Browse pgsql-admin by date

  From Date Subject
Next Message Stephan Szabo 2003-08-01 06:21:59 Re: Parallel transactions failing oddly
Previous Message Stephan Szabo 2003-08-01 06:07:53 Re: Parallel transactions failing oddly