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 again
Sorry, haven't looked into it. Since we already changed everything to = CASE on 9.2.0.4.0. The reason wasn't a bug but to be coherent with the = usage of DECODE / CASE. We agreed upon ANSI style stuff (INNER JOIN, = CASE blahblah) since 2 developers have a SQL Server background and seem = to comprehend that faster (no pun intended, they're great).
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:39 PM
An: oracle-l_at_freelists.org
Betreff: RE: Wrong results using decode when db upgraded to 9205
Thanks,
I can't imagine rewriting all decodes to case statements ... That alone would take more than 6-9 months in our code base.=3D20
Are there any bug# that you know?
Raj
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Stefan Jahnke
Sent: Wednesday, May 05, 2004 11:31 AM
To: oracle-l_at_freelists.org
Subject: 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 =3D3D 9.2.0.4.0 to 9.2.0.5.0 and as you said, CASE works fine. We have =3D3D rewritten all our DECODE statements to CASE and all of them still work. =3D3D So at with CASE there doesn't seem to be a problem.
Stefan
-----Urspr=3D3DFCngliche 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 ...=3D3D20 "and decode('C8','C8',237,0) =3D3D3D =
237" =3D
If
the same statement is =3D3D 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.=3D3D20 Any =3D
hearsay?
Known issues? Experiences?
Thanks
Raj
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html'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 put
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