-----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-----
