From: Date: February 24 2007 11:10pm
Subject: Re: MySQL Daylight Savings Time Patch - easy check
List-Archive: http://lists.mysql.com/mysql/205214
Message-Id: <000501c75860$93093f70$04fea8c0@DGGTPQ11>
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit

Ryan,

I just restart MySQL on the one box that was off, and bingo ... the 2 results 
are now the same. I think the system time zone was changed a while back, so 
after restarting, it set it back to the default "SYSTEM" setting.

Mickalo
----- Original Message ----- 
From: "Ryan Stille" <ryan@stripped>
To: <mysql@stripped>
Sent: Saturday, February 24, 2007 4:07 PM
Subject: Re: MySQL Daylight Savings Time Patch - easy check


> I'm not exactly sure what you should do, hence my earlier question about the 
> empty time zone tables.  I get the same (correct) result on both of my 
> servers - on one of them I've updated the MySQL time zone tables, and on the 
> other the tables are empty, always have been.  Hopefully someone will weigh in 
> on this.
>
> Is your OS updated?  On Linux you can check by running 'zdump -v 
> /etc/localtime | grep 2007'.  You should see some lines mentioning March 11.
>
> If your OS is not ready for the change, that could be your problem.
>
> You could also try updating the MySQL timezone tables, as was mentioned 
> earlier in this thread.  I did mine with this command:
> mysql_tzinfo_to_sql  /usr/share/zoneinfo | mysql mysql -p
>
> And yes I got a few errors, as other people have mentioned in this thread. 
> But they all appear to be related to overseas timezones so I'm not too 
> concerned about them.
>
> -Ryan
>
> Mike Blezien wrote:
>> Out of curiousity, what should be done if they results are different. We 
>> checked on one of boxes and got two different results:
>>
>> SELECT UNIX_TIMESTAMP('2007-03-11 02:00:00'),
>>    -> UNIX_TIMESTAMP('2007-03-11 03:00:00');
>> +---------------------------------------+---------------------------------------+
>> | UNIX_TIMESTAMP('2007-03-11 02:00:00') | UNIX_TIMESTAMP('2007-03-11 
>> 03:00:00') |
>> +---------------------------------------+---------------------------------------+
>> |                            1173600000 | 
>> 1173603600 |
>> +---------------------------------------+---------------------------------------+
>>
>> Thx's
>> Mickalo
>> ----- Original Message ----- From: "Ryan Stille" <ryan@stripped>
>> To: <mysql@stripped>
>> Sent: Saturday, February 24, 2007 3:28 PM
>> Subject: Re: MySQL Daylight Savings Time Patch - easy check
>>
>>
>>> Ryan Stille wrote:
>>>> Paul DuBois wrote:
>>>>> At 4:40 PM -0600 2/20/07, Ryan Stille wrote:
>>>>>> Is there an easy way to test to see if MySQL already has the proper 
>>>>>> tables loaded?
>>>>>>
>>>>>> -Ryan
>>>>>
>>>>> Yes, reload them. :-)  After that, they're current! .......
>>>>>
>>>
>>> After digging around on the net for a while I found an easy way to tell if 
>>> your MySQL installation is ready for the new daylight savings time.
>>>
>>> SELECT UNIX_TIMESTAMP('2007-03-11 02:00:00'),  UNIX_TIMESTAMP('2007-03-11 
>>> 03:00:00');
>>>
>>> This should return the same value, even though you are feeding it different 
>>> times, because this is when the 1 hr change occurs.  I get the correct 
>>> result on both of my machines.  On one of them I've run the suggested 
>>> |mysql_tzinfo_to_sql command, on the other, the time zone tables are 
>>> completely empty!
>>>
>>> Any wisdom on these time zone tables - are they ever used, should I populate 
>>> them or not?
>>>
>>> -Ryan