Re: migration from mysql 3.2.23 to 4.1.13

From: Miroslav Lachman (000.fbsd_at_quip.cz)
Date: 08/26/05

  • Next message: John Brooks: "IDE Raid Performance"
    Date: Fri, 26 Aug 2005 15:35:38 +0200
    To: ruben@bloemgarten.demon.nl
    
    

    Don't forget to repair all tables /databases befor dump.
    I recommend you to convert ISAM tables to MyISAM before dump. (but do it
    on backup copy of data, not on original)
    Dump databases by newer mysqldump.
    If you are using non latin1 charset, maybe you will have some troubles
    after importing dump into 4.1.
    Do not blindly dump and reimport mysql users (table `user` from database
    `mysql`) because 4.1 has different structure and using different
    passwords. Manualy recreate all accounts instead.

    Ruben Bloemgarten wrote:
    > Hi Mario,
    > The dump was done on 3.23. I'll give 4.1 a try on that machine, sounds like
    > a nice hack though,using mysqldump 4.1 on a 3.23 database. Thanks for the
    > tip.
    >
    > Ruben
    >
    > -----Original Message-----
    > From: mario [mailto:mario@schmut.com]
    > Sent: August 19, 2005 8:37 PM
    > To: ruben@bloemgarten.demon.nl
    > Cc: james@jpri.com; freebsd-isp@freebsd.org
    > Subject: RE: migration from mysql 3.2.23 to 4.1.13
    >
    > So, Ruben Bloemgarten wrote:
    >
    >>Hi James,
    >>
    >>That was the first thing I tried, unfortunately that does not work as
    >>the way 3.23 deals with ISAM is different to 4.1 and so it spits out
    >>errors when it runs into unrecognizable syntax. If you have managed to
    >>use mysqldump for a migration I would very much appreciate hearing about
    >>it as it would simplify things conisderably.
    >
    >
    > was this using mysldump 3.23 or 4.1? they produce different results and i
    > found one to work and the other not. i don't remember which did what but
    > just try the version you haven't yet.
    >
    > then there is also
    > http://dev.mysql.com/doc/mysql/en/upgrading-from-3-23.html
    > and then
    > http://dev.mysql.com/doc/mysql/en/upgrading-from-4-0.html
    >
    > looking at the docs, it seems, you need to do a bit more than just a dump.
    >
    > hope this helps. i remember going from 4.0 to 4.1 was already fun.
    >
    >
    > mario;>
    >
    >
    >
    >
    >
    _______________________________________________
    freebsd-isp@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-isp
    To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"


  • Next message: John Brooks: "IDE Raid Performance"

    Relevant Pages

    • RE: migration from mysql 3.2.23 to 4.1.13
      ... The dump was done on 3.23. ... a nice hack though,using mysqldump 4.1 on a 3.23 database. ... No virus found in this incoming message. ... Checked by AVG Anti-Virus. ...
      (freebsd-isp)
    • Re: OT: Problems importing SQL queries - drifting off in another direction...
      ... aware that mysqldump produced a nice lot of SQL commands. ... For some reason I was thinking it was going to be a dump of whatever binary format the database is stored as. ... Now this fails as it appears php requires the full path to the binary. ...
      (uk.comp.sys.mac)
    • Re: OT: Problems importing SQL queries - drifting off in another direction...
      ... aware that mysqldump produced a nice lot of SQL commands. ... For some reason I was thinking it was going to be a dump of whatever binary format the database is stored as. ... If you can start mysqldump on the command line from any folder without having to specify its full path then it's probably in a folder in your PATH. ...
      (uk.comp.sys.mac)
    • mysqldump
      ... I'm trying to do a dump of my database with one line for each INSERT: ... Is it possible to do it with mysqldump? ... Is there another tool do that under Linux? ...
      (comp.databases)