| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: Possible Y2K trap in using DECODE?
Shawn Ramsey wrote:
>
> 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.
Easy in your SQL Plus session - not so easy if you have the same code in 500 or so application programs... :)
Cheers
--
 |
 |