Hi,
On Wed, Jul 30, 2014 at 10:01 AM, Keith Medcalf <kmedc...@dessus.com> wrote:
> Store and retrieve everything in the database in Zulu time. Whether this
> means using timestrings, UNIX timestamps, JD or MJD floats is up to you. The
> application (user interface) is responsible for converting retrieved data to
> the "display timezone" on output and convert data from the "input timezone"
> on input.
>
> This is the only reliable way to handle multiple timezones. There are lots
> of moronic ways and five-nines (asctually more like nine-nines) of all
> software written use those moronic methods and for that reason do not work
> properly ("not work properly" being defined as anything somewhere between
> producing incorrect or ludicrously entertaining results and just puking all
> over the floor). In many cases "not working" but "not puking" is acceptable
> provided that the moronic behaviour is internally consistent. In others,
> "not working" is fatal.
Well, PostgreSQL's method for this to be handled at the
client/connection level seemed to have worked very well, and doesn't
seem very "moronic". Having this handled at the database level makes
the application(s) much less prone to bugs.
Thanks,
-will
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
