From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
---|---|
To: | Don Drake <dondrake(at)gmail(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: plpgsql functions and NULLs |
Date: | 2005-01-31 21:31:34 |
Message-ID: | 20050131132701.G12960@megazone.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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)
From | Date | Subject | |
---|---|---|---|
Next Message | Luiz Rafael Culik Guimaraes | 2005-01-31 21:54:45 | number os commands inside transaction block |
Previous Message | Thomas F.O'Connell | 2005-01-31 21:14:19 | Re: plpgsql functions and NULLs |