D
dbeavon
Guest
>> session:time-source = “some_connected_db” ? This was essentially how we used to design our ABL software. Unfortunately if a given database is used across multiple timezones, it didn't end up being a good solution. The timezone of the database is not necessarily a great reference point (especially when the server of the database observes daylight savings). We ended up settling on using UTC for storing absolute chronological date/time to the database. Every user has their own timezone. It is a not much more than preference. Showing a given date/time in a some (preferred) timezone is analogous to displaying a length that is formatted as feet or meters. By storing chonological datetime values as UTC (which doesn't respect daylight savings), it is more intuitive to convert back and forth to the user's preference of timezone. Even then, the API is not totally straightforward, and the semantics are a bit clunky. It would be nice to see some improvement. Perhaps I'll add an enhancement idea to create an OO wrapper...
Continue reading...
Continue reading...