Hmmm, interesting choice of errors. I noticed that when oracle got to 10gR2, ORA-01722, 01723 are not longer listed.... Think that means if you hold out long enough you'll be ok? :) Joel Patterson Database Administrator joel.patterson@xxxxxxxxxxx x72546 904 727-2546 -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Wolfgang Breitling Sent: Thursday, December 28, 2006 9:16 AM To: dbvision@xxxxxxxxxxxx Cc: oracle-l Subject: Re: [SPAM] 10gR2 Upgrade .. Watch out At 02:58 AM 12/28/2006, Nuno Souto wrote: >and that is precisely why there are so many shops >out there running very old releases of Oracle and no >plans whatsoever to upgrade. Because what they have now >works. And they are virtually assured by Oracle when they >upgrade the rdbms, the blessed thing WILL break their >applications. If that is the case then their applications ARE already broken, they just may not know it yet. And as Greg pointed out, the "brokenness" can become obvious at any moment even without an upgrade. Another popular application bug is to use the wrong datatype in predicates, e.g. character_column = 12345 and then come running when one day they get an ora-1722 error. "But it worked yesterday and I didn't change anything". Oracle can not - and should not - cater to all possible application bugs out there. I'd be satisfied if they look after their own bugs - like the overzealous order by elimination ( point 3 in the OP ). Regards Wolfgang Breitling Centrex Consulting Corporation www.centrexcc.com ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ -- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-l