after dating death mate traumatic - Ora 01722 invalid number updating date


Is there a way that I can not have to worry about which way my predicates are evaulated.

ora 01722 invalid number updating date-43

July 12, 2002 - am UTC The only sure fire way to avoid this in pretty much every language is: compare numbers to numbers, strings to strings, dates to dates, etc to etc....

always avoid the implicit conversion -- don't store numbers in varchar2's (i know, i know "its a generic model", well, generic models have their limited advantages -- and they have their very serious drawbacks). generic code = "pretty cool, but will it work" sometimes.... there rbo "works" and cbo "fails" but neither "fails" really - the query was wrong to begin with.

Be rearranging the order of the where clause i got it to work. If I have a domain table cg_ref_codes with fields domain, low_value, high_value, abbreviation, meaning (all varchar2).

If further some of my domains contain purely numeric values.

You can use case when ageband not in ( 'TOTALS', 'TO' ) then to_number(age Band) end instead of just to_number. or did you mean for me to change the view definition?