Re: Use of CURRENT_DATE vs SYSDATE and DST
- From: Janine Sisk <janine@xxxxxxxxxx>
- To: Thomas.Mercadante@xxxxxxxxxxxxxxxxx
- Date: Thu, 22 Mar 2007 13:54:04 -0700
On Mar 22, 2007, at 12:19 PM, Mercadante, Thomas F (LABOR) wrote:
So after patching my database with the current DST patch (and not
patching the client), the value of CURRENT_DATE is incorrect – it
is 15:14 right now. And what the heck does CURRENT_DATE return?
One hour ahead? I would expect it to be one hour behind (at 14:14)
until the end of March.
FWIW, in my unpatched 9.2.0.6 instance, these both return the correct
time. Maybe you've found a bug in the DST patch?
janine
- References:
- Use of CURRENT_DATE vs SYSDATE and DST
- From: Mercadante, Thomas F \(LABOR\)
Other related posts:
- » Use of CURRENT_DATE vs SYSDATE and DST
- » RE: Use of CURRENT_DATE vs SYSDATE and DST
- » RE: Use of CURRENT_DATE vs SYSDATE and DST
- » RE: Use of CURRENT_DATE vs SYSDATE and DST
- » Re: Use of CURRENT_DATE vs SYSDATE and DST
- » Re: Use of CURRENT_DATE vs SYSDATE and DST
- » RE: Use of CURRENT_DATE vs SYSDATE and DST
- » RE: Use of CURRENT_DATE vs SYSDATE and DST
- Use of CURRENT_DATE vs SYSDATE and DST
- From: Mercadante, Thomas F \(LABOR\)