[DB-SIG] DateTime: Changing the time value handling ?!

Jim Fulton jim.fulton@digicool.com
Wed, 11 Mar 1998 16:14:26 -0500

M.-A. Lemburg wrote:
> Jim Fulton wrote:
> >
> > M.-A. Lemburg wrote:
> > >
> > > When dealing with different time zones its better to have a
> > > set of specialized functions/classes. Time zone information
> > > is usually not stored together with date/time values. Most
> > > databases only work with broken down values and have no idea
> > > of the time zone the given values apply to. (And that's what
> > > I wrote the DateTime package for after all: to interface to
> > > databases ;-)
> >
> > ODMG stands for Object *Database* Management Group and the ODMG
> > standard I keep refering to and that includes time zone in its
> > Time and Timestamp classes is a *database* standard.
> I know, but the database APIs, I'm familiar with, don't support any time
> zone specific data interchange. They simply return the broken down
> values you stored -- without doing any conversions or time zone
> checking.
> How would I store the time zone offset in those databases ?

I guess you don't.  But that doesn't mean you shouldn't make it 
possible to handle the time zone (offset) in the underlying type.


Jim Fulton           mailto:jim@digicool.com
Technical Director   (888) 344-4332             Python Powered!
Digital Creations    http://www.digicool.com    http://www.python.org

Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email
address may not be added to any commercial mail list with out my
permission.  Violation of my privacy with advertising or SPAM will
result in a suit for a MINIMUM of $500 damages/incident, $1500 for

DB-SIG  - SIG on Tabular Databases in Python

send messages to: db-sig@python.org
administrivia to: db-sig-request@python.org