From: | Thomas F(dot)O'Connell <tfo(at)sitening(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:14:19 |
Message-ID: | c79ad2efbe563ca668dd7f9bea6be538@sitening.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
As far as I know, you didn't post your actual table definitions (or
full queries) earlier, so I'm not exactly sure what you mean.
-tfo
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-260-0005
On Jan 31, 2005, at 3:06 PM, Don Drake wrote:
> My outer query to get the candidates has an outer join, that works
> just fine and I get the null OMCR_ID's.
>
> It's when I have to query the dimension table (no joins) to see if a
> row exists with a (sometimes) null OMCR_ID I'm forced to write 2
> queries, when I think I should only have to write one.
>
> Thanks.
>
> -Don
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2005-01-31 21:31:34 | Re: plpgsql functions and NULLs |
Previous Message | Don Drake | 2005-01-31 21:06:34 | Re: plpgsql functions and NULLs |