Re: plpgsql functions and NULLs - Mailing list pgsql-sql

From Don Drake
Subject Re: plpgsql functions and NULLs
Date
Msg-id 6c21003b05013114272504d72e@mail.gmail.com
Whole thread Raw
In response to Re: plpgsql functions and NULLs  (Stephan Szabo <sszabo@megazone.bigpanda.com>)
Responses Re: plpgsql functions and NULLs  (Stephan Szabo <sszabo@megazone.bigpanda.com>)
List pgsql-sql
You learn something new everyday.  I've never seen that syntax before,
and it works like a charm!!

Thanks a ton.

-Don


On Mon, 31 Jan 2005 13:31:34 -0800 (PST), Stephan Szabo
<sszabo@megazone.bigpanda.com> wrote:
> 
> On Sun, 30 Jan 2005, Don Drake wrote:
> 
> > OK, I have a function that finds records that changed in a set of
> > tables and attempts to insert them into a data warehouse.
> >
> > There's a large outer loop of candidate rows and I inspect them to see
> > if the values really changed before inserting.
> >
> > My problem is that when I look to see if the row exists in the
> > warehouse already, based on some IDs, it fails when an ID is NULL.
> > The ID is nullable, so that's not a problem.
> >
> > But I'm forced to write an IF statement looking for the potential NULL
> > and write 2 queries:
> >
> > IF omcr_id is null
> >    select * from ....
> >    WHERE omcr_id is NULL
> >    AND ...
> > ELSE
> >    select * from ....
> >    WHERE omcr_id=candidate.omcr_id
> >    AND ....
> > END IF;
> 
> Hmm, perhaps some form like:
> 
> WHERE not(candidate.omcr_id is distinct from omcr_id)
> 
> 


-- 
Donald Drake
President
Drake Consulting
http://www.drakeconsult.com/
312-560-1574


pgsql-sql by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: number os commands inside transaction block
Next
From: "Luiz Rafael Culik Guimaraes"
Date:
Subject: Re: number os commands inside transaction block