RE: MySQL Daylight Savings Time Patch - easy check
Oops - I should have done /etc/init.d/mysql restart
Things are now working just fine. Thanks for the tip about restarting the
server!
UNIX_TIMESTAMP('2007-03-11 02:00:00') | UNIX_TIMESTAMP('2007-03-11
03:00:00')
--+-
-
1173596400 |
1173596400
Regards,
Jerry Schwartz
Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
> -Original Message-
> From: Ryan Stille [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 28, 2007 5:10 PM
> To: mysql@lists.mysql.com
> Subject: Re: MySQL Daylight Savings Time Patch - easy check
>
> I am on 4.1.20-1.
>
> Maybe your OS isn't patched?
>
> Try this: "SELECT @@global.time_zone;"
>
> If you get back "SYSTEM", then MySQL is looking to the OS for
> timezone
> data. And its only loaded when MySQL starts, so if you haven't
> restarted MySQL since you patched your OS, you need to do that.
>
> -Ryan
>
> Jerry Schwartz wrote:
> > What version of MySQL are you using? I'm running 4.1.21,
> and that check
> > doesn't work even after I've updated (I think) the time zone tables.
> >
> > I should probably eyeball the output of mysql_tzinfo_to_sql.
> >
> > Regards,
> >
> > Jerry Schwartz
> > Global Information Incorporated
> > 195 Farmington Ave.
> > Farmington, CT 06032
> >
> > 860.674.8796 / FAX: 860.674.8341
> >
> >
> >
> >> -Original Message-
> >> From: Ryan Stille [mailto:[EMAIL PROTECTED]
> >> Sent: Saturday, February 24, 2007 4:28 PM
> >> To: mysql@lists.mysql.com
> >> 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
> >>
> >> |
> >>
> >>
> >> --
> >> 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]
>
>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: MySQL Daylight Savings Time Patch - easy check
I'm still not having any luck. I did
shell> /etc.init.d/mysql reload
my @@global.time_zone is still SYSTEM, and yet I still get
UNIX_TIMESTAMP('2007-03-11 02:00:00') | UNIX_TIMESTAMP('2007-03-11
03:00:00')
--+-
-
1173596400 |
117360
shell> date -d "mar 11 02:00"
Sun Mar 11 03:00:00 EDT 2007
so my OS does have the right settings.
Regards,
Jerry Schwartz
Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
> -Original Message-
> From: Ryan Stille [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 28, 2007 5:10 PM
> To: mysql@lists.mysql.com
> Subject: Re: MySQL Daylight Savings Time Patch - easy check
>
> I am on 4.1.20-1.
>
> Maybe your OS isn't patched?
>
> Try this: "SELECT @@global.time_zone;"
>
> If you get back "SYSTEM", then MySQL is looking to the OS for
> timezone
> data. And its only loaded when MySQL starts, so if you haven't
> restarted MySQL since you patched your OS, you need to do that.
>
> -Ryan
>
> Jerry Schwartz wrote:
> > What version of MySQL are you using? I'm running 4.1.21,
> and that check
> > doesn't work even after I've updated (I think) the time zone tables.
> >
> > I should probably eyeball the output of mysql_tzinfo_to_sql.
> >
> > Regards,
> >
> > Jerry Schwartz
> > Global Information Incorporated
> > 195 Farmington Ave.
> > Farmington, CT 06032
> >
> > 860.674.8796 / FAX: 860.674.8341
> >
> >
> >
> >> -Original Message-
> >> From: Ryan Stille [mailto:[EMAIL PROTECTED]
> >> Sent: Saturday, February 24, 2007 4:28 PM
> >> To: mysql@lists.mysql.com
> >> 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
> >>
> >> |
> >>
> >>
> >> --
> >> 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]
>
>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL Daylight Savings Time Patch - easy check
Is MySQL on each one set to the same time zone?
SELECT@@global.time_zone;
-Ryan
Néstor wrote:
That was interesting. I have 2 rhel 3 servers and they both have been
update to handle the DST. They both yield different results when I
ran the
command:
SERVER=RALPH
+---+---+
| UNIX_TIMESTAMP('2007-03-11 02:00:00') | UNIX_TIMESTAMP('2007-03-11
03:00:00') |
+---+---+
| 1173607200 | 1173610800 |
+---+---
and this for the other server :
SERVER=MAGGIE
+---+---+
| UNIX_TIMESTAMP('2007-03-11 02:00:00') | UNIX_TIMESTAMP('2007-03-11
03:00:00') |
+---+---+
|1173607200 | 1173607200 |
+---+---
Uhm.
Nestor
On 2/28/07, William R. Mussatto <[EMAIL PROTECTED]> wrote:
On Wed, February 28, 2007 14:10, Ryan Stille said:
> I am on 4.1.20-1.
>
> Maybe your OS isn't patched?
>
> Try this: "SELECT @@global.time_zone;"
Won't help if you are on debian which is still on 4.0.
> If you get back "SYSTEM", then MySQL is looking to the OS for timezone
> data. And its only loaded when MySQL starts, so if you haven't
> restarted MySQL since you patched your OS, you need to do that.
>
> -Ryan
>
> Jerry Schwartz wrote:
>> What version of MySQL are you using? I'm running 4.1.21, and that
check
>> doesn't work even after I've updated (I think) the time zone tables.
>>
>> I should probably eyeball the output of mysql_tzinfo_to_sql.
>>
>> Regards,
>>
>> Jerry Schwartz
>> Global Information Incorporated
>> 195 Farmington Ave.
>> Farmington, CT 06032
>>
>> 860.674.8796 / FAX: 860.674.8341
>>
>>
>>
>>> -Original Message-
>>> From: Ryan Stille [mailto:[EMAIL PROTECTED]
>>> Sent: Saturday, February 24, 2007 4:28 PM
>>> To: mysql@lists.mysql.com
>>> 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
>>>
>>> |
>>>
>>>
>>> --
>>> 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]
>
>
--
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]
Re: MySQL Daylight Savings Time Patch - easy check
That was interesting. I have 2 rhel 3 servers and they both have been
update to handle the DST. They both yield different results when I ran the
command:
SERVER=RALPH
+---+---+
| UNIX_TIMESTAMP('2007-03-11 02:00:00') | UNIX_TIMESTAMP('2007-03-11
03:00:00') |
+---+---+
| 1173607200 | 1173610800 |
+---+---
and this for the other server :
SERVER=MAGGIE
+---+---+
| UNIX_TIMESTAMP('2007-03-11 02:00:00') | UNIX_TIMESTAMP('2007-03-11
03:00:00') |
+---+---+
|1173607200 | 1173607200 |
+---+---
Uhm.
Nestor
On 2/28/07, William R. Mussatto <[EMAIL PROTECTED]> wrote:
On Wed, February 28, 2007 14:10, Ryan Stille said:
> I am on 4.1.20-1.
>
> Maybe your OS isn't patched?
>
> Try this: "SELECT @@global.time_zone;"
Won't help if you are on debian which is still on 4.0.
> If you get back "SYSTEM", then MySQL is looking to the OS for timezone
> data. And its only loaded when MySQL starts, so if you haven't
> restarted MySQL since you patched your OS, you need to do that.
>
> -Ryan
>
> Jerry Schwartz wrote:
>> What version of MySQL are you using? I'm running 4.1.21, and that check
>> doesn't work even after I've updated (I think) the time zone tables.
>>
>> I should probably eyeball the output of mysql_tzinfo_to_sql.
>>
>> Regards,
>>
>> Jerry Schwartz
>> Global Information Incorporated
>> 195 Farmington Ave.
>> Farmington, CT 06032
>>
>> 860.674.8796 / FAX: 860.674.8341
>>
>>
>>
>>> -Original Message-
>>> From: Ryan Stille [mailto:[EMAIL PROTECTED]
>>> Sent: Saturday, February 24, 2007 4:28 PM
>>> To: mysql@lists.mysql.com
>>> 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
>>>
>>> |
>>>
>>>
>>> --
>>> 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]
>
>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL Daylight Savings Time Patch - easy check
On Wed, February 28, 2007 14:10, Ryan Stille said:
> I am on 4.1.20-1.
>
> Maybe your OS isn't patched?
>
> Try this: "SELECT @@global.time_zone;"
Won't help if you are on debian which is still on 4.0.
> If you get back "SYSTEM", then MySQL is looking to the OS for timezone
> data. And its only loaded when MySQL starts, so if you haven't
> restarted MySQL since you patched your OS, you need to do that.
>
> -Ryan
>
> Jerry Schwartz wrote:
>> What version of MySQL are you using? I'm running 4.1.21, and that check
>> doesn't work even after I've updated (I think) the time zone tables.
>>
>> I should probably eyeball the output of mysql_tzinfo_to_sql.
>>
>> Regards,
>>
>> Jerry Schwartz
>> Global Information Incorporated
>> 195 Farmington Ave.
>> Farmington, CT 06032
>>
>> 860.674.8796 / FAX: 860.674.8341
>>
>>
>>
>>> -Original Message-
>>> From: Ryan Stille [mailto:[EMAIL PROTECTED]
>>> Sent: Saturday, February 24, 2007 4:28 PM
>>> To: mysql@lists.mysql.com
>>> 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
>>>
>>> |
>>>
>>>
>>> --
>>> 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]
>
>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL Daylight Savings Time Patch - easy check
I am on 4.1.20-1.
Maybe your OS isn't patched?
Try this: "SELECT @@global.time_zone;"
If you get back "SYSTEM", then MySQL is looking to the OS for timezone
data. And its only loaded when MySQL starts, so if you haven't
restarted MySQL since you patched your OS, you need to do that.
-Ryan
Jerry Schwartz wrote:
What version of MySQL are you using? I'm running 4.1.21, and that check
doesn't work even after I've updated (I think) the time zone tables.
I should probably eyeball the output of mysql_tzinfo_to_sql.
Regards,
Jerry Schwartz
Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
-Original Message-
From: Ryan Stille [mailto:[EMAIL PROTECTED]
Sent: Saturday, February 24, 2007 4:28 PM
To: mysql@lists.mysql.com
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
|
--
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]
RE: MySQL Daylight Savings Time Patch - easy check
What version of MySQL are you using? I'm running 4.1.21, and that check
doesn't work even after I've updated (I think) the time zone tables.
I should probably eyeball the output of mysql_tzinfo_to_sql.
Regards,
Jerry Schwartz
Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
> -Original Message-
> From: Ryan Stille [mailto:[EMAIL PROTECTED]
> Sent: Saturday, February 24, 2007 4:28 PM
> To: mysql@lists.mysql.com
> 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
>
> |
>
>
> --
> 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]
Re: MySQL Daylight Savings Time Patch - easy check
- Original Message -
> *From:* Ryan Stille <[EMAIL PROTECTED]>
> *To:* mysql@lists.mysql.com
> *Date:* Sat, 24 Feb 2007 15:28:25 -0600
>
> 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
This may depend on where you live? I tried your select above and got
two different answers. Trying:
SELECT UNIX_TIMESTAMP('2007-03-25 01:00:00'),
UNIX_TIMESTAMP('2007-03-25 02:00:00');
which is when BST sets in in the UK (where I am), gave me identical
answers.
My 2 cents-worth
Terry
www.confexdb.co.uk
>
> |
>
>
> --
> 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]
Re: MySQL Daylight Savings Time Patch - easy check
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" <[EMAIL PROTECTED]>
To:
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') |
+---+---+
|117360 |
1173603600 |
+---+---+
Thx's
Mickalo
- Original Message ----- From: "Ryan Stille" <[EMAIL PROTECTED]>
To:
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
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
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') |
+---+---+
|117360 |
1173603600 |
+---+---+
Thx's
Mickalo
- Original Message - From: "Ryan Stille" <[EMAIL PROTECTED]>
To:
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
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL Daylight Savings Time Patch - easy check
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')
|
+---+---+
|117360 |1173603600
|
+---+---+
Thx's
Mickalo
- Original Message -
From: "Ryan Stille" <[EMAIL PROTECTED]>
To:
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
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
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
|
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL Daylight Savings Time Patch
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! ... My timezone tables appear to be empty. At least the time_zone_name and time_zone_transition tables are for sure. I was under the impression I needed to update these tables, but if its working fine without them, then. it must be looking to the OS for timezone info? -Ryan Probably should have included some more info about my setup. I'm on 4.1.20-1 on Linux. -Ryan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL Daylight Savings Time Patch
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! ... My timezone tables appear to be empty. At least the time_zone_name and time_zone_transition tables are for sure. I was under the impression I needed to update these tables, but if its working fine without them, then. it must be looking to the OS for timezone info? -Ryan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL Daylight Savings Time Patch
Yes they are; and 22 >= 3
- Original Message -
From: "Jerry Schwartz" <[EMAIL PROTECTED]>
To: "'Bryan S. Katz'" <[EMAIL PROTECTED]>;
Sent: Wednesday, February 21, 2007 10:30 AM
Subject: RE: MySQL Daylight Savings Time Patch
> Aren't the time zone tables new in 4.1.3?
>
> Regards,
>
> Jerry Schwartz
> Global Information Incorporated
> 195 Farmington Ave.
> Farmington, CT 06032
>
> 860.674.8796 / FAX: 860.674.8341
>
>
> > -Original Message-
> > From: Bryan S. Katz [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, February 20, 2007 9:03 PM
> > To: mysql@lists.mysql.com
> > Subject: Re: MySQL Daylight Savings Time Patch
> >
> > Same exact issue on v5.0.27.
> >
> > I installed another windows patch, that did nothing, but then
> > changed my
> > system clock to march 12th, and then back to present day. Now the DST
> > shifts are correct in the future and incorrect in the past.
> > I've destroyed
> > the timezone tables, and they made no difference. Which
> > means that they
> > were never being used.
> >
> > Any ideas?
> >
> >
> > - Original Message -
> > From: "Bryan S. Katz" <[EMAIL PROTECTED]>
> > To:
> > Sent: Tuesday, February 20, 2007 7:50 PM
> > Subject: MySQL Daylight Savings Time Patch
> >
> >
> > > Running 4.1.22, on windows 98, I'm having trouble getting
> > the time zone
> > > tables to actually work. I've loaded the tables as per:
> > > http://dev.mysql.com/downloads/timezones.html, and followed the
> > diagnostics
> > > as per: http://lists.mysql.com/mysql/205115
> > > .
> > >
> > > It appears that my results from said diagnostic indeed prove that my
> > tables
> > > are correct. However, I don't see those tables being used.
> > The following
> > > statements yield varying results on my linux/windows
> > machines (I run about
> > > ten servers).
> > >
> > > SELECT DATE_FORMAT(from_unixtime(unix_timestamp('2007-4-1
> > 00:00:00') +
> > > 2*60*60),'%H');
> > > SELECT DATE_FORMAT(from_unixtime(unix_timestamp('2007-3-11
> > 00:00:00') +
> > > 2*60*60),'%H');
> > > SELECT DATE_FORMAT(from_unixtime(unix_timestamp('2006-4-2
> > 00:00:00') +
> > > 2*60*60),'%H');
> > > SELECT DATE_FORMAT(from_unixtime(unix_timestamp('2006-3-12
> > 00:00:00') +
> > > 2*60*60),'%H');
> > >
> > > The linux machine -- with empty timezone tables is correct.
> > 2007-3-11 and
> > > 2006-4-2 result in midnight plus 2 hours being 3am --
> > correct in the past
> > > and correct in the future. On my modern XP machines, the future is
> > correct
> > > and the past is incorrect. On my older XP/98 machines, the past is
> > correct
> > > and the future is incorrect. It is on my 98 server that I
> > am now playing,
> > > having loaded timezone tables, and going crazy. I have
> > upgraded my win98
> > > timezones via a registry update.
> > >
> > >
> > > --
> > > 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]
> >
> >
>
>
>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL Daylight Savings Time Patch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 If it's any consolation, I got the exact same warnings. However, I don't know if it's normal either. - -- Skype: cannona MSN/Windows Messenger: [EMAIL PROTECTED] (don't send email to the hotmail address.) - - Original Message - From: "Jerry Schwartz" <[EMAIL PROTECTED]> To: "'Paul DuBois'" <[EMAIL PROTECTED]>; "'Sun, Jennifer'" <[EMAIL PROTECTED]>; "'Dan Buettner'" <[EMAIL PROTECTED]>; "'Chris White'" <[EMAIL PROTECTED]> Cc: Sent: Wednesday, February 21, 2007 8:45 AM Subject: RE: MySQL Daylight Savings Time Patch I just ran mysql_tzinfo_to_sql on a CentOS (Linux) system, and it complained about the various Riyadh time zones: Warning: Unable to load '/usr/share/zoneinfo/right/Mideast/Riyadh87' as time zone. Skipping it. Warning: Unable to load '/usr/share/zoneinfo/right/Mideast/Riyadh88' as time zone. Skipping it. Warning: Unable to load '/usr/share/zoneinfo/right/Mideast/Riyadh89' as time zone. Skipping it. etc. Any idea whether or not this is normal? Regards, Jerry Schwartz Global Information Incorporated 195 Farmington Ave. Farmington, CT 06032 860.674.8796 / FAX: 860.674.8341 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (MingW32) - GPGrelay v0.959 Comment: Key available from all major key servers. iD8DBQFF3GZ+I7J99hVZuJcRAvUUAJ4xHKNQtxYBSrpDqadTzPdBx3uQIwCfRZkL uQ5ODv/bD5SN5CW9JpYIlxQ= =z+FD -END PGP SIGNATURE- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: MySQL Daylight Savings Time Patch
Aren't the time zone tables new in 4.1.3?
Regards,
Jerry Schwartz
Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
> -Original Message-
> From: Bryan S. Katz [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 20, 2007 9:03 PM
> To: mysql@lists.mysql.com
> Subject: Re: MySQL Daylight Savings Time Patch
>
> Same exact issue on v5.0.27.
>
> I installed another windows patch, that did nothing, but then
> changed my
> system clock to march 12th, and then back to present day. Now the DST
> shifts are correct in the future and incorrect in the past.
> I've destroyed
> the timezone tables, and they made no difference. Which
> means that they
> were never being used.
>
> Any ideas?
>
>
> - Original Message -
> From: "Bryan S. Katz" <[EMAIL PROTECTED]>
> To:
> Sent: Tuesday, February 20, 2007 7:50 PM
> Subject: MySQL Daylight Savings Time Patch
>
>
> > Running 4.1.22, on windows 98, I'm having trouble getting
> the time zone
> > tables to actually work. I've loaded the tables as per:
> > http://dev.mysql.com/downloads/timezones.html, and followed the
> diagnostics
> > as per: http://lists.mysql.com/mysql/205115
> > .
> >
> > It appears that my results from said diagnostic indeed prove that my
> tables
> > are correct. However, I don't see those tables being used.
> The following
> > statements yield varying results on my linux/windows
> machines (I run about
> > ten servers).
> >
> > SELECT DATE_FORMAT(from_unixtime(unix_timestamp('2007-4-1
> 00:00:00') +
> > 2*60*60),'%H');
> > SELECT DATE_FORMAT(from_unixtime(unix_timestamp('2007-3-11
> 00:00:00') +
> > 2*60*60),'%H');
> > SELECT DATE_FORMAT(from_unixtime(unix_timestamp('2006-4-2
> 00:00:00') +
> > 2*60*60),'%H');
> > SELECT DATE_FORMAT(from_unixtime(unix_timestamp('2006-3-12
> 00:00:00') +
> > 2*60*60),'%H');
> >
> > The linux machine -- with empty timezone tables is correct.
> 2007-3-11 and
> > 2006-4-2 result in midnight plus 2 hours being 3am --
> correct in the past
> > and correct in the future. On my modern XP machines, the future is
> correct
> > and the past is incorrect. On my older XP/98 machines, the past is
> correct
> > and the future is incorrect. It is on my 98 server that I
> am now playing,
> > having loaded timezone tables, and going crazy. I have
> upgraded my win98
> > timezones via a registry update.
> >
> >
> > --
> > 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]
>
>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: MySQL Daylight Savings Time Patch
I just ran mysql_tzinfo_to_sql on a CentOS (Linux) system, and it complained about the various Riyadh time zones: Warning: Unable to load '/usr/share/zoneinfo/right/Mideast/Riyadh87' as time zone. Skipping it. Warning: Unable to load '/usr/share/zoneinfo/right/Mideast/Riyadh88' as time zone. Skipping it. Warning: Unable to load '/usr/share/zoneinfo/right/Mideast/Riyadh89' as time zone. Skipping it. etc. Any idea whether or not this is normal? Regards, Jerry Schwartz Global Information Incorporated 195 Farmington Ave. Farmington, CT 06032 860.674.8796 / FAX: 860.674.8341 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: MySQL Daylight Savings Time Patch
I think that's only true if the server is using the default system time zone. In addition, you can set a per-connection time zone and use time zone sensitive functions such as CONVERT_TZ(). All of these mean that MySQL needs to be aware of time zone definitions. There could also be trouble if you are using replication across time zones, I suspect. There are explicit instructions for building time zone tables in section 5.9.8 of the manual. Regards, Jerry Schwartz Global Information Incorporated 195 Farmington Ave. Farmington, CT 06032 860.674.8796 / FAX: 860.674.8341 > -Original Message- > From: Paul DuBois [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 20, 2007 5:17 PM > To: Sun, Jennifer; [EMAIL PROTECTED]; mysql@lists.mysql.com > Subject: RE: MySQL Daylight Savings Time Patch > > At 4:36 PM -0500 2/20/07, Sun, Jennifer wrote: > >Any answers for the question below ? > > > >Is there a DST patch for MySql 4.0.20? Thanks. > > > >-Original Message- > >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > >Sent: Friday, February 09, 2007 9:30 AM > >To: mysql@lists.mysql.com > >Subject: MySQL Daylight Savings Time Patch > > > >Is there a DST patch for MySQL 4.0.x series? > > > >I've been getting scary emails from our sys and net admins about > >impending > >doom. > > > >Thanks, > > > >David > > Before MySQL 4.1.3, the server gets its time zone from the > operating system > at startup. The time zone can be specified explicitly by > setting the TZ > TZ environment variable setting, or by using the --timezone > option to the > mysqld_safe server startup script. > > Assuming that the server host itself has had its operating > system updated > to handle the new Daylight Saving Time rules, that should be > all that's > necessary for MySQL to know the correct time. > > -- > Paul DuBois, MySQL Documentation Team > Madison, Wisconsin, USA > MySQL AB, www.mysql.com > > -- > 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]
Re: MySQL Daylight Savings Time Patch
Same exact issue on v5.0.27.
I installed another windows patch, that did nothing, but then changed my
system clock to march 12th, and then back to present day. Now the DST
shifts are correct in the future and incorrect in the past. I've destroyed
the timezone tables, and they made no difference. Which means that they
were never being used.
Any ideas?
- Original Message -
From: "Bryan S. Katz" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, February 20, 2007 7:50 PM
Subject: MySQL Daylight Savings Time Patch
> Running 4.1.22, on windows 98, I'm having trouble getting the time zone
> tables to actually work. I've loaded the tables as per:
> http://dev.mysql.com/downloads/timezones.html, and followed the
diagnostics
> as per: http://lists.mysql.com/mysql/205115
> .
>
> It appears that my results from said diagnostic indeed prove that my
tables
> are correct. However, I don't see those tables being used. The following
> statements yield varying results on my linux/windows machines (I run about
> ten servers).
>
> SELECT DATE_FORMAT(from_unixtime(unix_timestamp('2007-4-1 00:00:00') +
> 2*60*60),'%H');
> SELECT DATE_FORMAT(from_unixtime(unix_timestamp('2007-3-11 00:00:00') +
> 2*60*60),'%H');
> SELECT DATE_FORMAT(from_unixtime(unix_timestamp('2006-4-2 00:00:00') +
> 2*60*60),'%H');
> SELECT DATE_FORMAT(from_unixtime(unix_timestamp('2006-3-12 00:00:00') +
> 2*60*60),'%H');
>
> The linux machine -- with empty timezone tables is correct. 2007-3-11 and
> 2006-4-2 result in midnight plus 2 hours being 3am -- correct in the past
> and correct in the future. On my modern XP machines, the future is
correct
> and the past is incorrect. On my older XP/98 machines, the past is
correct
> and the future is incorrect. It is on my 98 server that I am now playing,
> having loaded timezone tables, and going crazy. I have upgraded my win98
> timezones via a registry update.
>
>
> --
> 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]
Re: MySQL Daylight Savings Time Patch
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! If you really want a non-reload test, you can do something like this (Credits: This example comes from Peter Gulutzan) Find out the time zone id for the region: mysql> select * from mysql.time_zone_name -> where Name = 'America/Edmonton'; ++--+ | Name | Time_zone_id | ++--+ | America/Edmonton | 100 | ++--+ 1 row in set (0.97 sec) Find out the transition dates for that zone in this year: mysql> select * from time_zone_transition -> where Time_zone_id = -> and Transition_time between 1167634800 and 1199170799 -> order by Time_zone_id,Transition_time; +--+-++ | Time_zone_id | Transition_time | Transition_type_id | +--+-++ | 100 | 1175418000 | 1 | | 100 | 1193558400 | 2 | +--+-++ 2 rows in set (0.00 sec) Find out what '1175418000' and '1193558400' mean: mysql> select from_unixtime(1175418000); +---+ | from_unixtime(1175418000) | +---+ | 2007-04-01 03:00:00 | +---+ 1 row in set (0.00 sec) mysql> select from_unixtime(1193558400); +---+ | from_unixtime(1193558400) | +---+ | 2007-10-28 01:00:00 | +---+ 1 row in set (0.00 sec) Diagnosis: this database thinks the switch is on April 1, which is wrong. Cure: update your operating system files, check the "MySQL Server Time Zone Support" section of the manual, and update the table. So, as you can see, it's probably easier just to reload the files. Paul DuBois wrote: At 4:17 PM -0600 2/20/07, Paul DuBois wrote: At 4:36 PM -0500 2/20/07, Sun, Jennifer wrote: Any answers for the question below ? Is there a DST patch for MySql 4.0.20? Thanks. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, February 09, 2007 9:30 AM To: mysql@lists.mysql.com Subject: MySQL Daylight Savings Time Patch Is there a DST patch for MySQL 4.0.x series? I've been getting scary emails from our sys and net admins about impending doom. Thanks, David Before MySQL 4.1.3, the server gets its time zone from the operating system at startup. The time zone can be specified explicitly by setting the TZ TZ environment variable setting, or by using the --timezone option to the mysqld_safe server startup script. Assuming that the server host itself has had its operating system updated to handle the new Daylight Saving Time rules, that should be all that's necessary for MySQL to know the correct time. I should mention also: For those of you running 4.1.3 or later, to get your MySQL server to know about the new DST rules, you should make sure your OS is updated with the new zoneinfo files, and then reload those files into MySQL with mysql_tzinfo_to_sql. See: http://dev.mysql.com/doc/mysql/en/time-zone-support.html Particularly the Note in the middle of the page and the last few paragraphs. You may have previously loaded your system's zoneinfo files into MySQL, but when those zoneinfo files are updated, the changes do not automatically propagate to MySQL's time zone tables. You must reload the tables to update them. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- Paul DuBois, MySQL Documentation Team Madison, Wisconsin, USA MySQL AB, www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL Daylight Savings Time Patch
Is there an easy way to test to see if MySQL already has the proper tables loaded? -Ryan Paul DuBois wrote: At 4:17 PM -0600 2/20/07, Paul DuBois wrote: At 4:36 PM -0500 2/20/07, Sun, Jennifer wrote: Any answers for the question below ? Is there a DST patch for MySql 4.0.20? Thanks. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, February 09, 2007 9:30 AM To: mysql@lists.mysql.com Subject: MySQL Daylight Savings Time Patch Is there a DST patch for MySQL 4.0.x series? I've been getting scary emails from our sys and net admins about impending doom. Thanks, David Before MySQL 4.1.3, the server gets its time zone from the operating system at startup. The time zone can be specified explicitly by setting the TZ TZ environment variable setting, or by using the --timezone option to the mysqld_safe server startup script. Assuming that the server host itself has had its operating system updated to handle the new Daylight Saving Time rules, that should be all that's necessary for MySQL to know the correct time. I should mention also: For those of you running 4.1.3 or later, to get your MySQL server to know about the new DST rules, you should make sure your OS is updated with the new zoneinfo files, and then reload those files into MySQL with mysql_tzinfo_to_sql. See: http://dev.mysql.com/doc/mysql/en/time-zone-support.html Particularly the Note in the middle of the page and the last few paragraphs. You may have previously loaded your system's zoneinfo files into MySQL, but when those zoneinfo files are updated, the changes do not automatically propagate to MySQL's time zone tables. You must reload the tables to update them. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: MySQL Daylight Savings Time Patch
At 5:08 PM -0500 2/20/07, Sun, Jennifer wrote: Thanks. Below is the notes from the version 5 manual, does that mean after I patch my OS, I may need to reload the timezone tables ? How I can determine that I have to reload the timezone tables, not might need? Or will it hurt anything if I just reload the tables anyway? Thanks. Just go ahead and reload them. If you look at the output of mysql_tzinfo_to_sql, you'll notice that the first thing is does is TRUNCATE TABLE for the time zone tables, so that they start out in a pristine state before the new information gets loaded into them. Note Loading the time zone information is not necessarily a one-time operation because the information changes occasionally. For example, the rules for Daylight Saving Time in the United States, Mexico, and parts of Canada changed in 2007. When such changes occur, applications that use the old rules become out of date and you may find it necessary to reload the time zone tables to keep the information used by your MySQL server current. See the notes at the end of this section. -- Paul DuBois, MySQL Documentation Team Madison, Wisconsin, USA MySQL AB, www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: MySQL Daylight Savings Time Patch
At 4:17 PM -0600 2/20/07, Paul DuBois wrote: At 4:36 PM -0500 2/20/07, Sun, Jennifer wrote: Any answers for the question below ? Is there a DST patch for MySql 4.0.20? Thanks. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, February 09, 2007 9:30 AM To: mysql@lists.mysql.com Subject: MySQL Daylight Savings Time Patch Is there a DST patch for MySQL 4.0.x series? I've been getting scary emails from our sys and net admins about impending doom. Thanks, David Before MySQL 4.1.3, the server gets its time zone from the operating system at startup. The time zone can be specified explicitly by setting the TZ TZ environment variable setting, or by using the --timezone option to the mysqld_safe server startup script. Assuming that the server host itself has had its operating system updated to handle the new Daylight Saving Time rules, that should be all that's necessary for MySQL to know the correct time. I should mention also: For those of you running 4.1.3 or later, to get your MySQL server to know about the new DST rules, you should make sure your OS is updated with the new zoneinfo files, and then reload those files into MySQL with mysql_tzinfo_to_sql. See: http://dev.mysql.com/doc/mysql/en/time-zone-support.html Particularly the Note in the middle of the page and the last few paragraphs. You may have previously loaded your system's zoneinfo files into MySQL, but when those zoneinfo files are updated, the changes do not automatically propagate to MySQL's time zone tables. You must reload the tables to update them. -- Paul DuBois, MySQL Documentation Team Madison, Wisconsin, USA MySQL AB, www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: MySQL Daylight Savings Time Patch
At 4:36 PM -0500 2/20/07, Sun, Jennifer wrote: Any answers for the question below ? Is there a DST patch for MySql 4.0.20? Thanks. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, February 09, 2007 9:30 AM To: mysql@lists.mysql.com Subject: MySQL Daylight Savings Time Patch Is there a DST patch for MySQL 4.0.x series? I've been getting scary emails from our sys and net admins about impending doom. Thanks, David Before MySQL 4.1.3, the server gets its time zone from the operating system at startup. The time zone can be specified explicitly by setting the TZ TZ environment variable setting, or by using the --timezone option to the mysqld_safe server startup script. Assuming that the server host itself has had its operating system updated to handle the new Daylight Saving Time rules, that should be all that's necessary for MySQL to know the correct time. -- Paul DuBois, MySQL Documentation Team Madison, Wisconsin, USA MySQL AB, www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: MySQL Daylight Savings Time Patch
Thanks. Below is the notes from the version 5 manual, does that mean after I patch my OS, I may need to reload the timezone tables ? How I can determine that I have to reload the timezone tables, not might need? Or will it hurt anything if I just reload the tables anyway? Thanks. Note Loading the time zone information is not necessarily a one-time operation because the information changes occasionally. For example, the rules for Daylight Saving Time in the United States, Mexico, and parts of Canada changed in 2007. When such changes occur, applications that use the old rules become out of date and you may find it necessary to reload the time zone tables to keep the information used by your MySQL server current. See the notes at the end of this section. -Original Message- From: Dan Buettner [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 20, 2007 5:03 PM To: Chris White Cc: mysql@lists.mysql.com Subject: Re: MySQL Daylight Savings Time Patch NTP won't solve this problem for you. NTP, as well as most computer clocks, know nothing about daylight savings time, or about time zones. What they know is how many seconds have elapsed since "the epoch". The epoch, in the case of most UNIX-based OSes, is midnight January 1, 1970. I think Windows is the same. The original Mac OS was 1/1/1904, for example. It's up to the operating system to apply rules that determine that X number of seconds (as reported by the clock hardware) since the epoch translates to some human time, based on local settings for time zone and with any daylight savings time rules for that time zone applied. My understanding is that MySQL needs no patch, but your underlying OS most likely does. I know there have been patches issued for Solaris 2.x, 9 and 10, Windows XP, and Mac OS X 10.4, and almost certainly others. HTH, Dan On 2/20/07, Chris White <[EMAIL PROTECTED]> wrote: > > Sun, Jennifer wrote: > > Any answers for the question below ? > > > > Is there a DST patch for MySql 4.0.20? Thanks. > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Friday, February 09, 2007 9:30 AM > > To: mysql@lists.mysql.com > > Subject: MySQL Daylight Savings Time Patch > > > > Is there a DST patch for MySQL 4.0.x series? > > > > I've been getting scary emails from our sys and net admins about > > impending > > doom. > > > > Thanks, > > > > David > > If you're using NTP then what's the problem? Sync to one of the ntp > pools, boom your clocks are updated, MySQL uses system time and yay. > I'm fairly sure you could sync 500 server this way. > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > >
Re: MySQL Daylight Savings Time Patch
NTP won't solve this problem for you. NTP, as well as most computer clocks, know nothing about daylight savings time, or about time zones. What they know is how many seconds have elapsed since "the epoch". The epoch, in the case of most UNIX-based OSes, is midnight January 1, 1970. I think Windows is the same. The original Mac OS was 1/1/1904, for example. It's up to the operating system to apply rules that determine that X number of seconds (as reported by the clock hardware) since the epoch translates to some human time, based on local settings for time zone and with any daylight savings time rules for that time zone applied. My understanding is that MySQL needs no patch, but your underlying OS most likely does. I know there have been patches issued for Solaris 2.x, 9 and 10, Windows XP, and Mac OS X 10.4, and almost certainly others. HTH, Dan On 2/20/07, Chris White <[EMAIL PROTECTED]> wrote: Sun, Jennifer wrote: > Any answers for the question below ? > > Is there a DST patch for MySql 4.0.20? Thanks. > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, February 09, 2007 9:30 AM > To: mysql@lists.mysql.com > Subject: MySQL Daylight Savings Time Patch > > Is there a DST patch for MySQL 4.0.x series? > > I've been getting scary emails from our sys and net admins about > impending > doom. > > Thanks, > > David If you're using NTP then what's the problem? Sync to one of the ntp pools, boom your clocks are updated, MySQL uses system time and yay. I'm fairly sure you could sync 500 server this way. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL Daylight Savings Time Patch
Sun, Jennifer wrote: Any answers for the question below ? Is there a DST patch for MySql 4.0.20? Thanks. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, February 09, 2007 9:30 AM To: mysql@lists.mysql.com Subject: MySQL Daylight Savings Time Patch Is there a DST patch for MySQL 4.0.x series? I've been getting scary emails from our sys and net admins about impending doom. Thanks, David If you're using NTP then what's the problem? Sync to one of the ntp pools, boom your clocks are updated, MySQL uses system time and yay. I'm fairly sure you could sync 500 server this way. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: MySQL Daylight Savings Time Patch
Any answers for the question below ? Is there a DST patch for MySql 4.0.20? Thanks. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, February 09, 2007 9:30 AM To: mysql@lists.mysql.com Subject: MySQL Daylight Savings Time Patch Is there a DST patch for MySQL 4.0.x series? I've been getting scary emails from our sys and net admins about impending doom. Thanks, David -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
