From: | Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com> |
---|---|
To: | John Morgan <jdmorgan(at)unca(dot)edu> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: case statement to cath nulls on joined tables |
Date: | 2012-02-03 15:05:39 |
Message-ID: | CAJghg4+Uk2+Dh6smvG2n8-xKGCLGT7Ltx_c-cXP3_Gbm6O0RXQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Try that:
SELECT address, CASE WHEN value_of_interest IS NULL THEN 'more friendly
message' ELSE value_of_interest END value_of_interest
>From poly_table left outer join data_table one poly_table.common_id =
data_table.common_id
--
Matheus de Oliveira
On Fri, Feb 3, 2012 at 10:45 AM, John Morgan <jdmorgan(at)unca(dot)edu> wrote:
> Hello,
>
> I am doing a left outer join between a polygon table and a data table.
> Everything
> returns fine from this join as expected. However, there are cases where
> there isn?t data for a given polygon and this return as the expected null
> in the result set. I would like to utilize something like a case statement
> to catch the nulls and return a ?more friendly? message. I have tried
> unsuccessfully to use the following logic:
>
> *Select case value_of_interest null then ?more friendly message? else
> value_of_interest end*
>
> *From poly_table left outer join data_table one poly_table.common_id =
> data_table.common_id*
>
> If someone could let me know where I am going wrong it would be greatly
> appreciated.
>
> Cheers,
>
> Derek
>
From | Date | Subject | |
---|---|---|---|
Next Message | Matheus de Oliveira | 2012-02-03 15:09:21 | Re: case statement to cath nulls on joined tables |
Previous Message | John Morgan | 2012-02-03 12:45:37 | case statement to cath nulls on joined tables |