There was some discussion on supporting timezones (TZ for short) in
datetime fields, maybe it's important enough to have a separated discussion.
For the record at this point most people seem to want UTC in database
(me too).
Another thing to consider and that I've not seen in previous discussion
is that daylight saving _change_ during human history (MySQL had his own
table of TZ that could go easily out of sync with the real world #1).
lets go with enum:
Pro of TZ stored in datetime fields
- The TZ is fixed at storage time and will be remembered 4ever
- Is ready to use, no additional function to convert it
- The database does not need to convert times at storage time
Pro of pure UTC datetime
- More compact storage, may be even stored in BIGINT or DOUBLE if sub
second resolution is needed
- Easier/faster to JOIN, no conversion needed during join operation.
- More portable between different geographical location
- It's more UNIX ;)
#1 Require a lazy DBA, but every DBA is lazy
--
regards, Francesco (vivo) Riosa
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
