Hi Sheeri
On 27/08/2008, at 9:30 AM, Sheeri K. Cabral wrote:
I think we (developers, dbas, etc) have to stop thinking about time
as we experience it, and accept that timezones are a presentation
issue. It makes things a whole lot easier if you separate the
functionality of time with the presentation of it -- it also helps
when dealing with folks who code in times instead of using database
functions for time -- which ends up having problems when the web/
application servers are not time sync'd (or in particularly poor
programming, when they're in different time zones).
So, if you want to retrieve or store a time (including "now"),
that's a database function. If you want to display a time, that's a
presentation layer function. (there are cases in which I'd be OK
with application code determining time, but that's only for queries
that otherwise would take forever. If you start with having one
centralized definitive time server (which I'm making the database
here for simplification) it will lead to much less confusion in the
long run).
Excellent description!
It's like user-specific CSS.
Cheers,
Arjen.
--
Arjen Lentz, Founder @ Open Query
Training and Expertise for MySQL in Australia and New Zealand
http://openquery.com.au/training/ (ph. +61-7-3103 0809)
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
