Hi,
why not using the -e otion to mysqldump ? it make an INSERT command as
long as your max_command_packet permit it.
2005/8/23, Bruce Dembecki <[EMAIL PROTECTED]>:
> Once you decide to use mysqldump, be aware that the quickest way to
> export/import large files is to use the --tab feature on ex
hi,
should I use mysqldump from the Mysql 4.0 or 4.1?
Regards,
Rafal
p.s.
Thx for all other tips!
At 21:44 23.08.2005, Bruce Dembecki wrote:
Once you decide to use mysqldump, be aware that the quickest way to
export/import large files is to use the --tab feature on export and
mysqlimport to l
Once you decide to use mysqldump, be aware that the quickest way to
export/import large files is to use the --tab feature on export and
mysqlimport to load the data...
Essentially:
On the old (4.0) server:
mysqldump --tab=/var/tmp/directory mydatabase
On the new (4.1) server (assuming you
Hello.
Use mysqldump, but be aware of incompatibles between 4.0 and 4.1:
http://dev.mysql.com/doc/mysql/en/upgrading-from-4-0.html
Rafal Kedziorski <[EMAIL PROTECTED]> wrote:
> Hi,
>
> we have an J2EE application which ist using MySQL 4.0. There is an
> bug, which was fixed in MySQL
At 15:30 23.08.2005, Jason Pyeron wrote:
Would I be correct in assuming you need to minimize down time on a
productions system? Or are you just asking how to upgrade?
Correct, I wan't minimize downtime :)
Regards,
Rafal
On Tue, 23 Aug 2005, Rafal Kedziorski wrote:
Hi,
we have an J2EE app
AFAIK, to move the data from one InnoDB file to one table per file,
the only option is to dump and restore.
(you may want to remove index, and foreign key checks before the
restore, and put it back afterwards)
2005/8/23, Rafal Kedziorski <[EMAIL PROTECTED]>:
> Hi,
>
> we have an J2EE application
Would I be correct in assuming you need to minimize down time on a
productions system? Or are you just asking how to upgrade?
On Tue, 23 Aug 2005, Rafal Kedziorski wrote:
Hi,
we have an J2EE application which ist using MySQL 4.0. There is an bug, which
was fixed in MySQL 4.1. We are using tr
