On Tue, Dec 30, 2008 at 9:27 PM, Mark Atwood <[email protected]> wrote: > > On Dec 24, 2008, at 3:43 AM, Roy Lyseng wrote: >> >> Unfortunately, 4 bits is too small for a time-zone specification (unless >> you allow maximum 16 timezones to be used ;) So a timestamp WITH time zone >> probably has to go in more than 8 bytes. > > > I am not a fan of keeping TZ information as a deep part of the server. The > complexity of the Olson TZ database coding system and database is on it's > face evidence that TZ stuff should be data driven, external, and part of > presentation layers, not storage layers. Keep all dates inside the db in > UTC and be done with it.
Agreed. There was an earlier thread or five about TZ support. When I started asking about microsecond precision I did not intend to reintroduce the (IMO inappropriate) idea of timezones as a property of values stored in the database. _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
