RE: data type conversion in 10g

It's not the difference in Oracle's versions that causing a problem.  

THe reason you get an error in one case (and not another) is that in one table all the values in "test1" field are "convertable" into numbers, while in the other table (which happened to be under different oracle version) there is one (or more) values in "test1" column which could not be converted into numbere - hence could not be compaired with the number "88".  

Igor

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of David Boyd Sent: Tuesday, July 03, 2007 1:43 PM
To: oracle-l_at_freelists.org
Subject: data type conversion in 10g

We have Oracle 10.2.0.3. There is one field, test1 that is definite as char(2). When we use 'where test1<88', it works fine in 9i, but we get 'ORA-01722 invalid number' error in 10g. Once I add single quotes around 88, the error is gone. I know the best practice is not to use implicit conversion. Just wonder why it works in 9i, but not in 10g, more restriction in 10g or if there is any change in 10g that causes the error tracked?

See what you're getting into...before you go there. Check it out! <http://newlivehotmail.com>

--
http://www.freelists.org/webpage/oracle-l