As for me, /etc/localtime -> /usr/share/zoneinfo/EST5DST Which should be correct for my system as I am located in that time zone. I don't understand why MySQL doesn't give the same UNIX_TIMESTAMP for "2007-03-11 02:00:00" and "2007-03-11 03:00:00". Just to make sure, I tried it with one minute earlier and one minute later and got the same results.
Regards, Jerry Schwartz Global Information Incorporated 195 Farmington Ave. Farmington, CT 06032 860.674.8796 / FAX: 860.674.8341 > -----Original Message----- > From: Jean-Sebastien Pilon [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 28, 2007 12:53 PM > To: mysql@lists.mysql.com > Subject: RE: Does MySQL require patch for Daylight Savings > Time 2007 change > > You have both compare 0100 vs 0200 and 0200 vs 0300 in my > reply... It wasn't clear because of emails being wrapped at 80 chars. > > And it still doesn't work after loading the tables with > mysql_tzinfo_to_sql > > And /etc/localtime is a symlink to the proper tz file ? > > Jean-Sébastien Pilon > Systems Administrator > Penson Financial Services Canada Inc. > % Tel.: 514.841.9724 #269 > % Cell: 514.771.0365 > > > -----Original Message----- > > From: Jerry Schwartz [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, February 28, 2007 12:13 PM > > To: Jean-Sebastien Pilon; 'Causevic, Dzenan'; mysql@lists.mysql.com > > Subject: RE: Does MySQL require patch for Daylight Savings > > Time 2007 change > > > > Hang on a second! Doesn't EST transition to DST at 03:00? > > Shouldn't that > > query (the one for testing MySQL's time zones) be > > > > SELECT UNIX_TIMESTAMP('2007-03-11 > > 02:00:00'),UNIX_TIMESTAMP('2007-03-11 > > 03:00:00'); > > > > ? Nonetheless, it doesn't work for me. I get a one-hour > > difference, just as > > though the DST transition never existed. My time_zone > > variable is set to > > SYSTEM, and I've verified using zdump (Linux) that the time > > zone tables on > > my server are correct. I have loaded the latest time zone > > information using > > > > mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root mysql > > > > although it gave me some errors about Riyadh. > > > > Regards, > > > > Jerry Schwartz > > Global Information Incorporated > > 195 Farmington Ave. > > Farmington, CT 06032 > > > > 860.674.8796 / FAX: 860.674.8341 > > > > > > > -----Original Message----- > > > From: Jean-Sebastien Pilon [mailto:[EMAIL PROTECTED] > > > Sent: Wednesday, February 28, 2007 10:55 AM > > > To: Causevic, Dzenan; mysql@lists.mysql.com > > > Subject: RE: Does MySQL require patch for Daylight Savings > > > Time 2007 change > > > > > > I don't believe so, since the version of MySQL you are > > using relies on > > > the system's time. I am using 4.1 and I am setup to use > > system's time > > > and my timezone tables in the mysql schema are empty. I > would take a > > > look at those on your installation. You can also run the > 2nd command > > > below to see if the system returns proper time, both unix > timestamp > > > should be equal... > > > > > > mysql> SHOW VARIABLES LIKE 'time_zone'; > > > +---------------+--------+ > > > | Variable_name | Value | > > > +---------------+--------+ > > > | time_zone | SYSTEM | > > > +---------------+--------+ > > > 1 row in set (0.00 sec) > > > > > > > > > mysql> SELECT UNIX_TIMESTAMP('2007-03-11 > > > 01:00:00'),UNIX_TIMESTAMP('2007-03-11 02:00:00'); > > > +---------------------------------------+--------------------- > > > ---------- > > > --------+ > > > | UNIX_TIMESTAMP('2007-03-11 01:00:00') | > UNIX_TIMESTAMP('2007-03-11 > > > 02:00:00') | > > > +---------------------------------------+--------------------- > > > ---------- > > > --------+ > > > | 1173592800 | > > > 1173596400 | > > > +---------------------------------------+--------------------- > > > ---------- > > > --------+ > > > 1 row in set (0.00 sec) > > > > > > mysql> 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') | > > > +---------------------------------------+--------------------- > > > ---------- > > > --------+ > > > | 1173596400 | > > > 1173596400 | > > > +---------------------------------------+--------------------- > > > ---------- > > > --------+ > > > 1 row in set (0.00 sec) > > > > > > > > > > -----Original Message----- > > > > From: Causevic, Dzenan [mailto:[EMAIL PROTECTED] > > > > Sent: Wednesday, February 28, 2007 10:22 AM > > > > To: mysql@lists.mysql.com > > > > Subject: FW: Does MySQL require patch for Daylight Savings > > > > Time 2007 change > > > > > > > > Okay but after I patch OS do I still need to load time zone > > > > tables with > > > > following command: > > > > > > > > shell> mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u > > root mysql > > > > > > > > Is this still necessary? > > > > > > > > _______________________________ > > > > Dzenan Causevic > > > > Web Applications Developer > > > > NaviSite, Inc. > > > > 315-453-2912 x5346 (Office) > > > > 315-278-7371 (Cell) > > > > www.NaviSite.com > > > > > > > > > > > > -----Original Message----- > > > > From: J.R. Bullington [mailto:[EMAIL PROTECTED] > > > > Sent: Wednesday, February 28, 2007 9:40 AM > > > > To: mysql@lists.mysql.com > > > > Subject: re: Does MySQL require patch for Daylight > > Savings Time 2007 > > > > change > > > > > > > > > > > > As far as I know, MySQL does not need a > TZ patch (unless > > > > you use specific/custom Time Zone information), but > your OS does. > > > > > > > > The best way to check is to run: > > > > > > > > mysql> SHOW VARIABLES LIKE 'TIME_ZONE'; > > > > > > > > If it says SYSTEM, then you need only patch your OS. > > > > (Patching the OS is > > > > [OT] for this list). > > > > > > > > Here's the section from the manual in regards to 3.23 > Time Zones. > > > > > > > > http://dev.mysql.com/doc/refman/4.1/en/time-zone-support.html > > > > > > > > J.R. > > > > > > > NOTICE: This email contains privileged and confidential > > > information and is intended only for the individual to whom > > > it is addressed. If you are not the named addressee, you > > > should not disseminate, distribute or copy this e-mail. > > > Please notify the sender immediately by e-mail if you have > > > received this transmission by mistake and delete this > > > communication from your system. E-mail transmission cannot be > > > guaranteed to be secured or error-free as information could > > > be intercepted, corrupted, lost, destroyed, arrive late or > > > incomplete, or contain viruses. > > > > > > AVIS: Le prisent courriel contient des renseignements de > > > nature priviligiie et confidentielle et nest destini qu'` la > > > personne ` qui il est adressi. Si vous njtes pas le > > > destinataire privu, vous jtes par les prisentes avisis que > > > toute diffusion, distribution ou reproduction de cette > > > communication est strictement interdite. Si vous avez regu > > > ce courriel par erreur, veuillez en aviser immidiatement > > > lexpiditeur et le supprimer de votre systhme. Notez que la > > > transmission de courriel ne peut en aucun cas jtre considiri > > > comme inviolable ou exempt derreur puisque les informations > > > quil contient pourraient jtre interceptis, corrompues, > > > perdues, ditruites, arrivies en retard ou incomplhtes ou > > > contenir un virus. > > > > > > -- > > > 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]
