From: Date: August 10 2004 4:01pm
Subject: Re: timestamps
List-Archive: http://lists.mysql.com/java/7760
Message-Id: <230101c47ee2$7d39dfb0$155110ac@hebis>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

Jeff,

http://dev.mysql.com/doc/mysql/en/InnoDB_news-4.1.4.html

If you recreated the TIMESTAMP table in 4.1.3, then you have recreate it
again when you upgrade to >= 4.1.4.

Regards,

Heikki

----- Alkuperäinen viesti ----- 
Lähettäjä: "Jeff Mathis" <jmathis@stripped>
Vastaanottaja: "Heikki Tuuri" <Heikki.Tuuri@stripped>
Kopio: "Mark Matthews" <mark@stripped>; <java@stripped>
Lähetetty: Monday, August 09, 2004 10:40 PM
Aihe: Re: timestamps


> when did 4.1.4 come out? as of last week, we couldn't see it on the
> website. at any rate, it was only a minor inconvenience. we've moved on,
> and everything appears stable right now.
>
> thanks for your repsonse
>
> jeff
> Heikki Tuuri wrote:
> > Jeff,
> >
> > please look at the changelog of InnoDB-4.1.4 in the MySQL manual.
> >
> > An upgrade 4.0 --> 4.1.4 or later does NOT need any TIMESTAMP
conversion.
> >
> > It is a bug in 4.1.0 to 4.1.3.
> >
> > Regards,
> >
> > Heikki
> >
> > ----- Alkuperäinen viesti ----- 
> > Lähettäjä: "Jeff Mathis" <jmathis@stripped>
> > Vastaanottaja: "Mark Matthews" <mark@stripped>
> > Kopio: <java@stripped>; "Heikki Tuuri" <Heikki.Tuuri@stripped>
> > Lähetetty: Wednesday, August 04, 2004 10:31 PM
> > Aihe: Re: timestamps
> >
> >
> >
> >>yes, they are innodb tables. i populated the new time_zone tables using
> >>the system time zone files as per the manual recommendations, but, alas,
> >>no change.
> >>
> >>are you saying that its all messed up? dumping and reloading really
> >>isn't the greatest option  :(
> >>
> >>jeff
> >>Mark Matthews wrote:
> >>
> >>>-----BEGIN PGP SIGNED MESSAGE-----
> >>>Hash: SHA1
> >>>
> >>>Jeff Mathis wrote:
> >>>| hello,
> >>>|
> >>>| sorry if this is a know issue. we just upgraded our server from 4.0.4
> >
> > to
> >
> >>>| 4.1.3, and are now using the 3.1.3 CJ release.
> >>>|
> >>>| i noticed that after the upgrade, all our timestamp columns are
wrong!
> >>>|
> >>>| | 2036-07-09 05:45:55 |
> >>>| | 2036-07-15 05:42:42 |
> >>>| | 2036-07-15 05:42:45 |
> >>>| | 2036-07-15 05:42:45 |
> >>>| | 2036-07-16 05:42:35 |
> >>>|
> >>>| everything is wrong; the year, month and day. what happened? anyone
> >
> > else
> >
> >>>| seen this?
> >>>|
> >>>| jeff
> >>>|
> >>>
> >>>Jeff...Are these InnoDB tables? (If so, unfortunately it looks like
> >>>you'll have to dump and re-load, from what I hear).
> >>>
> >>>    -Mark
> >>>
> >>>- --
> >>>Mr. Mark Matthews
> >>>MySQL AB, Software Development Manager, J2EE and Windows Platforms
> >>>Office: +1 708 332 0507
> >>>www.mysql.com
> >>>
> >>>MySQL Guide to Lower TCO
> >>>http://www.mysql.com/it-resources/white-papers/tco.php
> >>>-----BEGIN PGP SIGNATURE-----
> >>>Version: GnuPG v1.2.3 (MingW32)
> >>>Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> >>>
> >>>iD8DBQFBETGItvXNTca6JD8RArFgAKCBlujs3RqozStFLCn2Fkyf7AuzFwCgkHA6
> >>>6bshoNnrkKIjVOgIrjn8fHw=
> >>>=5HFm
> >>>-----END PGP SIGNATURE-----
> >>>
> >>
> >>
> >>-- 
> >>Jeff Mathis, Ph.D. 505-955-1434
> >>Prediction Company jmathis@stripped
> >>525 Camino de los Marquez, Ste 6 http://www.predict.com
> >>Santa Fe, NM 87505
> >>
> >
> >
> >
>
>
> -- 
> Jeff Mathis, Ph.D. 505-955-1434
> Prediction Company jmathis@stripped
> 525 Camino de los Marquez, Ste 6 http://www.predict.com
> Santa Fe, NM 87505
>