Re: time zone leap seconds

[Jeff Mathis]

i seemed to have gotten around it by manually sourcing the script to 
update the password field, which had the create table statements in it, 
and then loading time zones based on our system time zone files. the 
manual section on upgrading from 4.0 to 4.1 did explain this -- i just 
had to dig a little bit to find it.

a frustrating issue is that all of my timestamp columns got monged 
(we're using innodb tables). all years got set to the year 2036. in 
poking around on the java list group I got the impression this is a 
known issue with innodb tables when migrating from 4.0.x to 4.1.x  :(

oh well. its not that mission critical, and I executed a database wide 
update to set all timestamp columns to current_timestamp(). at least 
i'll know when we did the upgrade.

jeff
Victor Pendleton wrote:
There is are five new time_% tables. You could install 4.1.3 in a clean
area, export the tables and import the tables into the upgraded environment.
You could also export your 4.0.x data and import this data into the newly
created 4.1.3 environment. 

-----Original Message-----
From: Jeff Mathis
To: mysql
Sent: 8/4/04 11:14 AM
Subject: time zone leap seconds
we just upgraded from 4.0.4 to 4.1.3, and are getting this warning. is 
there a script somewhere we can run to create the alleged missing time 
zone table?

040804 10:09:49  Warning: Can't open time zone table: Table 
'mysql.time_zone_leap_second' doesn't exist trying to live without them

thanks
jeff

--
Jeff Mathis, Ph.D.                      505-955-1434
Prediction Company                      [EMAIL PROTECTED]
525 Camino de los Marquez, Ste 6        http://www.predict.com
Santa Fe, NM 87505
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]