* Jochem van Dieten
The proper way to program this would require MySQL to support the AT TIME ZONE construct, but I haven't found it on the MySQL roadmap yet.
Woudn't the "proper way" be the way that leads to a result you can live with? Of course support in the server would have been better, but why can you not use a mechanism as described above?
Using AT TIME ZONE is the way supported by SQL:1999, which makes it the proper way.
Functionally, I believe it is much cleaner as it abstracts the problem away from the developer. Especially around DST changes this can be an important issue.
Jochem
--
I don't get it
immigrants don't work
and steal our jobs
- Loesje
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
