Re: Possible Y2K trap in using DECODE?

Snip

>Like you said earlier, your problem comes from the implicit converts from
date
>to varchar (and vice versa) using the default date format. You could
change
>the default date format, but since it can be changed by each user and thus
>override your system setting this wouldn't guarantee a solution (though it
>could be acceptable). The other solution, which doesn't rely on a "magic"
>value such as 'xyzab_-', is to make sure there are no implicit conversions:

Why not just explicitly set the date format in the sql*plus session? Just do an ALTER SESSION SET NLS_DATE_FORMAT 'DDMMYYYY' then there will be no question on the conversion. Received on Tue Jan 12 1999 - 11:39:24 CST