Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> AW: Wrong results using decode when db upgraded to 9205
Hi Rajendra
I don't know wether this helps or not: We upgraded a dev db from = 9.2.0.4.0 to 9.2.0.5.0 and as you said, CASE works fine. We have = rewritten all our DECODE statements to CASE and all of them still work. = So at with CASE there doesn't seem to be a problem.
Stefan
-----Urspr=FCngliche Nachricht-----
Von: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]Im Auftrag von Jamadagni, Rajendra
Gesendet: Wednesday, May 05, 2004 5:26 PM
An: oracle-l_at_freelists.org
Betreff: Wrong results using decode when db upgraded to 9205
I upgraded a dev db from 9202 to 9205 and one query with a DECODE
statement is giving wrong results. The whole query is big, but decode
statement looks like ...=20
"and decode('C8','C8',237,0) =3D 237" If the same statement is =
re-written
using case it works fine. I am searching on metablink but wanted to
check here first. This same query with same decode statement works fine
on 9202 database.=20
Any hearsay? Known issues? Experiences?
Thanks
Raj
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.htmlput 'unsubscribe' in the subject line.
-----------------------------------------------------------------
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request_at_freelists.org