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 str
On 7 Aug 2003 at 16:12, Andy Jackman wrote:
> >> 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 ga
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 - tha
On 7 Aug 2003 at 9:47, woody at nfri dot com wrote:
> While I don't know for sure, my guess is that it would have something
> to do with 32 bit as the magic number, but also...being that this
> won't become a problem until
>
> mysql> select from_unixtime(2147483647);
> +-
While I don't know for sure, my guess is that it would have something to
do with 32 bit as the magic number, but also...being that this won't
become a problem until
mysql> select from_unixtime(2147483647);
+---+
| from_unixtime(2147483647) |
+---+
|
