>
> Is this a bug? Should I file a bug at http://bugs.mysql.com/ ?
Yes this is a bug. It was already reported as #7515 "from_unixtime(0)
now returns NULL instead of the epoch". So no need to report it once
more. It will be fixed ASAP.
Anyway, thank you for raising this question once agai
? (I'd be happy
> to report if that's the case).
This is definitely a bug, which I have reported to MySQL bug-system as:
http://bugs.mysql.com/bug.php?id=7308
Meanwhile you can try to use STR_TO_DATE() function as temporary work-around.
Thanks for noticing this!
--
Dmitri Lenev,
tibility with previous MySQL's versions.
3) Actually I think user's time zone and not client time zone is what
important. Yes in case of some kind of GUI client they are the same
but for most of web-applications they are not.
So it is application responsibility to set MySQL session's time zone
what it needs. There is no special C API function for setting session's
time zone - one should use ordinary mysql_query/mysql_real_query() call
and "SET @@time_zone:=..." statement (which is equivalent to
"SET @@session.time_zone:=...") instead.
Hope this makes all these a bit more clear. Thank you for your interest
in these features and especially for your hint about mysqldump!
--
Dmitri Lenev, Software Developer
MySQL AB, www.mysql.com
Are you MySQL certified? http://www.mysql.com/certification
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
