RE: Oracle and DST changes
- From: <Joel.Patterson@xxxxxxxxxxx>
- To: <don@xxxxxxxxx>
- Date: Wed, 24 Jan 2007 10:59:24 -0500
The last place I worked, all our databases where set to GMT, (+00:00).
That however, was because they wanted all clients worldwide to operate
that way as it was a airline reservations scheduling application.
If you were to use the timestamp with local time zone datatype, then of
course your local time zone would be GMT, (when you might want it to be
Wisconsin).
A caveat is once you use the timestamp with <> time zone data types, you
can no longer change the DBTIMEZONE with a simple statement. You have
to go through procedures that will convert (recalculate) the data --
similar to what is happening here with the DST change.
Joel Patterson
Database Administrator
joel.patterson@xxxxxxxxxxx
x72546
904 727-2546
-----Original Message-----
From: dtseiler@xxxxxxxxx [mailto:dtseiler@xxxxxxxxx] On Behalf Of Don
Seiler
Sent: Wednesday, January 24, 2007 10:53 AM
To: Patterson, Joel
Cc: mgogala@xxxxxxxxxxx; wjwagman@xxxxxxxxxxx;
Thomas.Mercadante@xxxxxxxxxxxxxxxxx; gkatteri@xxxxxxxxxxx;
strickland.mark@xxxxxxxxx; John.Fedock@xxxxxxxxxxxx;
oracle-l@xxxxxxxxxxxxx
Subject: Re: Oracle and DST changes
We're in Wisconsin, USA, but our DBTIMEZONE has always been "+00:00".
I assume this is GMT, which is outside of the jurisdiction of the US
congress. Is there a need in this case for the Oracle patch? We're
currently on 10.2.0.2 on RHEL3.
Obviously we don't use any timezone-dependent data in our
applications. Is there a con to not properly setting the DBTIMEZONE?
Don.
On 1/24/07, Joel.Patterson@xxxxxxxxxxx <Joel.Patterson@xxxxxxxxxxx>
wrote:
> That's funny :)
>
> Except if Arizona is using those data types and needs to calculate the
> time a flight will take between destinatins... It needs to know when
and
> how much and keep it's data accurate.
>
> BTW Kabul is 10.5 off GMT, No DST, but who cares, they're cuckoo, (as
> in strange, very unconventional... hmmn wait that's me... but then
again
> at least I'm not living in one of the few countries left in the world
> that doesn't switch on the hour).
>
>
>
> Joel Patterson
> Database Administrator
> joel.patterson@xxxxxxxxxxx
> x72546
> 904 727-2546
>
> -----Original Message-----
> From: oracle-l-bounce@xxxxxxxxxxxxx
> [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Mladen Gogala
> Sent: Wednesday, January 24, 2007 8:59 AM
> To: wjwagman@xxxxxxxxxxx
> Cc: Thomas.Mercadante@xxxxxxxxxxxxxxxxx; gkatteri@xxxxxxxxxxx; Mark
> Strickland; John.Fedock@xxxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
> Subject: Re: Oracle and DST changes
>
> On 01/23/2007 11:52:37 AM, William Wagman wrote:
> > Greetings,
> >
> > I have been looking at the Metalink notes and am not clear I
> understand
> > when it becomes necesary to upgrade the clients. If one is only
using
> > the networking pieces of the clients and sqlplus is it going to be
> > necessary to upgrade the client in that case. I guess the general
> > question is, what client pieces will require the upgrade?
> >
>
>
> You should move to Arizona, it doesn't have DST. It has plenty of
> daylight as it is, and
> it is one of the few states that doesn't implement DST.
>
> --
> Mladen Gogala
> http://www.mladen-gogala.com
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
