Re: Interesting difference between nvl() and coalesce()
From: Stefan Koehler <contact_at_soocs.de>
Date: Sun, 8 Dec 2019 09:25:33 +0100 (CET)
Message-ID: <445293694.94093.1575793533657_at_ox.hosteurope.de>
Date: Sun, 8 Dec 2019 09:25:33 +0100 (CET)
Message-ID: <445293694.94093.1575793533657_at_ox.hosteurope.de>
Hello Stefan,
ah OK. Just to get the complete picture, please be also aware about the impact on the CBO if you gonna change the code.
https://jonathanlewis.wordpress.com/2018/02/13/coalesce-v-nvl/
Best Regards
Stefan Koehler
Independent Oracle performance consultant and researcher
Website: http://www.soocs.de
Twitter: _at_OracleSK
> Stefan Knecht <knecht.stefan_at_gmail.com> hat am 8. Dezember 2019 um 09:20 geschrieben:
>
>
> Perhaps to add a bit of detail - here it wasn't just a performance thing. It literally broke the code, because we have logic in the function that's called in the second argument of nvl(), and that logic is only valid if the first argument that came in, was indeed NULL.
>
> Sigh.
-- http://www.freelists.org/webpage/oracle-lReceived on Sun Dec 08 2019 - 09:25:33 CET