Re: MySQL Daylight Savings Time Patch

2007-02-21 Thread Bryan S. Katz
Yes they are; and 22 = 3

- Original Message - 
From: Jerry Schwartz [EMAIL PROTECTED]
To: 'Bryan S. Katz' [EMAIL PROTECTED];
mysql@lists.mysql.com
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: mysql@lists.mysql.com
  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]



MySQL Daylight Savings Time Patch

2007-02-20 Thread Bryan S. Katz
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]



Re: MySQL Daylight Savings Time Patch

2007-02-20 Thread Bryan S. Katz
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: mysql@lists.mysql.com
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]