-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Victor, thanks for responding. I really need help here.
I export/import the database using mysqldump (for exporting), and the mysql command (for importing). One thing to be noted thought, the exported sql has correct timestamps (they're exactly the same when in still the database). Also, I found another interesting thing: When I modified the timestamps in the dumpfile, adding '00' at the end, example: from 0404121921 into 040412912100, it got imported correctly. What gives? I'm thinking of hacking the dumpfile adding '00' at the end of every timestamp. On Tuesday 20 April 2004 08:49 pm, Victor Pendleton wrote: > How are you exporting/importing the data? > > -----Original Message----- > From: Fajar Priyanto > To: [EMAIL PROTECTED] > Sent: 4/20/04 3:51 AM > Subject: error importing date > > Hi all, > I encounter this error when importing database from one mysql server > into > another: the date imported is wrong. The type is timestamp. > > In the dump file, the date is : 0404121921, but when imported, it > becomes: > 0004041219. > > Could anybody pls give me direction why is that and how to correct it? > Thanks. > > The old mysql server is v. 4.0.13, and the new is 4.0.15. > One more info, I notice that the timezone is different, in the old: > JAVT, and > in the new: WIT. > > -- > Fajar Priyanto | Reg'd Linux User #327841 | http://linux.arinet.org > 15:47:50 up 7:38, Mandrake Linux release 9.2 (FiveStar) for i586 > public key: https://www.arinet.org/fajar-pub.key - -- Fajar Priyanto | Reg'd Linux User #327841 | http://linux.arinet.org 21:11:56 up 45 min, Mandrake Linux release 9.2 (FiveStar) for i586 public key: https://www.arinet.org/fajar-pub.key -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAhTCjkp5CsIXuxqURAhVGAJ90w9pULCucBiJ6Eay6avWqBteWPQCfQarM BpxA5MMayy8zdApxCfXDhec= =CUBy -----END PGP SIGNATURE----- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
