Daniel Kasak wrote:
Paul DuBois wrote:
If you have problems reloading the table due to the order
in which the InnoDB tables appear in the dump files, add
SET FOREIGN_KEY_CHECKS = 0;
to the beginning of the file before reloading it.
Our backups are quick large - over 500 MB. Opening the file an
At 10:33 AM +1000 9/18/03, Daniel Kasak wrote:
Paul DuBois wrote:
If you have problems reloading the table due to the order
in which the InnoDB tables appear in the dump files, add
SET FOREIGN_KEY_CHECKS = 0;
to the beginning of the file before reloading it.
Our backups are quick large - over 50
Paul DuBois wrote:
If you have problems reloading the table due to the order
in which the InnoDB tables appear in the dump files, add
SET FOREIGN_KEY_CHECKS = 0;
to the beginning of the file before reloading it.
Our backups are quick large - over 500 MB. Opening the file and adding
the above li
At 7:13 PM -0400 9/16/03, Irwin Boutboul wrote:
It looks like the dump works... however the way it is made, there is no
way to use it to recreate the database because key constraints fail. The
dump contains table creations in an order which does not respect key
constraints.
If you have problems r
It looks like the dump works... however the way it is made, there is no
way to use it to recreate the database because key constraints fail. The
dump contains table creations in an order which does not respect key
constraints.
Is there any work around to rebuild a database with innodb tables ?
