Keith, >> or is there some summertime adjustment occurring? You're right the -3600 looks like 1 hour of summertime and our server IS set to BST (1 hour ahead of GMT - sorry I can never figure out if that is -0100 or +0100). However, the same function gave different results a few minutes apart - that's the scary bit. - Andy
"Keith C. Ivey" wrote: > > On 7 Aug 2003 at 15:27, Andy Jackman wrote: > > > 1) I was investigating the unix_timestamp routine in mysql (version > > 3.23.46-nt) and for some reason the unix epoch (1-1-1970) was returned > > with a value of -3600. > > That's what I'd expect if the time zone was set to -0100, since > MySQL assumes the string represents a date-time in the server time > zone. Is your server set to GMT, or is there some summertime > adjustment occurring? > > > 2) The function > > from_unixtime(n) wraps on my server after 2^31 seconds. e.g. select > > from_unixtime(2147483648) returns "1900-01-00 00:00:00". > > Odd, on mine it gives "1901-12-13 15:45:52", which is the same as > FROM_UNIXTIME(-2147483648), which is what I would expect if the > argument to FROM_UNIXTIME() is a signed integer. > > -- > Keith C. Ivey <[EMAIL PROTECTED]> > Tobacco Documents Online > http://tobaccodocuments.org > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
