Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: daylight saving -> global database
Glen -=20
you don't mention the platform, but on unix you can slowly adjust the =
system
clock (forward or back) using date -a. with this approach 1:30AM =
should
only happen once if that's the problem you need to avoid. can't tell =
if
that's the concern or not.
this might be stating the obvious - but why not store the data using a
relative time that does not fluctuate strangely twice a year? avoid =
the
problem.
that said - i once worked with an application where out of order =
timestamps
would have been disastrous. the timestamps were localtime. the =
solution
there was to shut the application down for a couple hours each fall to =
let
all the messed up time between 1am and 2am go by un-noticed ;) AFAIK =
they
still do that. apps like this do happen...
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org]On Behalf Of bernas, glen
> Sent: Wednesday, November 03, 2004 2:10 PM
> To: oracle-l_at_freelists.org
> Subject: daylight saving -> global database
>=20 >=20
>=20
>=20
>=20 >=20 >=20 >=20 >=20 >=20
> ____________________________________________
>=20
>=20
> Phone:=20
> Direct: (508) 249-2237
> Ext: 42237
>=20 >=20 >=20 >=20
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Nov 03 2004 - 15:07:19 CST
![]() |
![]() |