mysql restore problem

Using mysql5.7 a database backup made using mysqldump fails because of errors on duplicate (foreign) key definitions

When restoring i had to resort to a workaround based on a clean set of database tables generated by akaunting itself.

Now instead of droping the tables and recreating them i truncate the respective tables and then insert the data.

SET FOREIGN_KEY_CHECKS=0;

LOCK TABLES `lxt_accounts` WRITE;

TRUNCATE TABLE `lxt_accounts`;

/*!40000 ALTER TABLE `lxt_accounts` DISABLE KEYS */;

INSERT INTO `lxt_accounts` VALUES ......

( repeat this for all tables )

 

in a typical mysql dump the TRUNCATE line is added, and the parts with te table droping and recreation are removed.



Can anyone advise on a more sensible way of restoring a database ?

<p>Using mysql5.7 a database backup made using mysqldump fails because of errors on duplicate (foreign) key definitions</p><br /> <p>When restoring i had to resort to a workaround based on a clean set of database tables generated by akaunting itself.<br /><br />Now instead of droping the tables and recreating them i truncate the respective tables and then insert the data.</p><br /> <p><br />SET FOREIGN_KEY_CHECKS=0;</p><br /> <p><br />LOCK TABLES `lxt_accounts` WRITE;</p><br /> <p>TRUNCATE TABLE `lxt_accounts`;</p><br /> <p>/*!40000 ALTER TABLE `lxt_accounts` DISABLE KEYS */;</p><br /> <p>INSERT INTO `lxt_accounts` VALUES ......<br /><br />( repeat this for all tables )</p><br /> <p> </p><br /> <p>in a typical mysql dump the TRUNCATE line is added, and the parts with te table droping and recreation are removed.<br /><br /><br /><br />Can anyone advise on a more sensible way of restoring a database ?</p>