From: | Don Drake <dondrake(at)gmail(dot)com> |
---|---|
To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: plpgsql functions and NULLs |
Date: | 2005-01-31 22:27:25 |
Message-ID: | 6c21003b05013114272504d72e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)megazone(dot)bigpanda(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Luiz Rafael Culik Guimaraes | 2005-01-31 22:29:42 | Re: number os commands inside transaction block |
Previous Message | Michael Fuhr | 2005-01-31 22:13:06 | Re: number os commands inside transaction block |