From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: isnull() function in pgAdmin3 |
Date: | 2016-09-28 14:54:54 |
Message-ID: | nsgljr$ip5$1@blaine.gmane.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
dudedoe01 schrieb am 27.09.2016 um 19:04:
> I am trying to emulate the isnull() function used in MySQL into postreSQL. I
> have tried different ways such is null but it's not producing the results
> desired. I am doing a data migration from MySQL into postgreSQL and need
> help with the isnull() in pgAdmin3.
>
> Any assistance provided would be greatly appreciated.
>
> Thanks,
>
> In MySQL:
>
> (case
> when
> ((`s`.`Funding_Date` = '')
> and (isnull(`s`.`Actual_Close_Date`)
> or (`s`.`Actual_Close_Date` = '')))
> then
> 'RPG_INV'
> when
> ((isnull(`s`.`Funding_Date`)
> or (`s`.`Funding_Date` <> ''))
> and ((`s`.`Actual_Close_Date` = '')
> or isnull(`s`.`Actual_Close_Date`)))
> then
> 'Builder_Inventory'
> else 'Owner_Inventory'
> end) AS `Lot_Status`,
>
Unrelated, but: why are you storing DATEs in VARCHAR columns?
A migration might be a good moment to clean up the data model and store DATEs in a DATE (or TIMESTAMP) column.
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2016-09-28 15:56:37 | Re: isnull() function in pgAdmin3 |
Previous Message | Adrian Klaver | 2016-09-28 14:50:34 | Re: isnull() function in pgAdmin3 |