* Jochem van Dieten > > 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.
I don't dispute that, but as I am not a mysql developer I can't easily do anything about it. > 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. I agree again. But it doesn't answer my question... I suppose you can live without timezones untill mysql supports it in the server? :) -- Roger -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
