Re: Avoiding ORA-01722 Invalid Number

Hi,
 the original poster did not want to change his design - that would have been the only reasonable answer though.  This will full-scan the table each time, does not account for special characters, end perform this expensive computation for each and every row in the table.

 (TM) not a good idea - this will break exept for the smallest databases.

 <rant> i hate to see these 'fancy' solutions from so-called object-designers that cannot tell the difference between numeric datatypes and alphanumeric. Ever thought about using the correct datatype for what you want to do ? i.e. numbers for numbers, dates for dates etc. Pretty advanced concept i guess. </rant>

in your case between '20' and '30' would have helped though... Received on Tue Jun 07 2005 - 02:16:51 CDT