By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,469 Members | 1,259 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,469 IT Pros & Developers. It's quick & easy.

InnoDB constraints and database restore

P: n/a
We use InnoDB tables and foreign key constraints extensively. The mysqldump
backs up the database tables in alphabetical order with foreign key
constraints defined in the create statement of each table. These foreign key
constraints are violated at the time of restore. We have tried the following
two solutions...

(1) We have tried to backup the database tables in the order of their
dependencies. This works but the backup scripts need to be maintained
carefully as new tables are added/removed from the database.

(2) phpMyAdmin export does the database dump and puts the table constraints
as ALTER statements at the end of the dump. Unfortunately, the phpMyAdmin
dumps cannot be automated and I have not been able to push constraints to
the end of the backup using mysqldump.

Any thoughts on how to handle this situation would be greatly appreciated.
Jul 20 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.