Complete Inserts vs Extended Inserts in phpMyAdmin
Exporting MySQL data from phpMyAdmin can be a challenge, especially when the tables are big. But most of the time, the MySQL dumps become humongous due to the form of the SQLs that are being exported. For example, the standard export would generate SQL along the likes of:
INSERT INTO `table` VALUES(1, ‘Bob’);
INSERT INTO `table` VALUES(2, ‘Brad’);
INSERT INTO `table` VALUES(3, ‘Ben’);
phpMyAdmin offers the option of Complete Inserts, and Extended Inserts. What do they mean?
Complete Inserts generate SQLs that are more readable, by including the table fields in each SQL line:
INSERT INTO `table` (`id`, `name`) VALUES(1, ‘Bob’);
INSERT INTO `table` (`id`, `name`) VALUES(2, ‘Brad’);
INSERT INTO `table` (`id`, `name`) VALUES(3, ‘Ben’);
Extended Inserts provide simplicity – instead of 3 lines (or 3,000), they combine all into one:
INSERT INTO `table` VALUES (1, ‘Bob’), (2, ‘Brad’), (3, ‘Ben’);
To get the best of both worlds – readability and brevity, we can select both options to generate SQLs like such:
INSERT INTO `table` (`id`, `name`) VALUES (1, ‘Bob’), (2, ‘Brad’), (3, ‘Ben’);
Imagine the file size savings! The newer phpMyAdmin versions already have both options checked, so it’s really a no-brainer to use.
Via Scriptalicious
Note: If you use BigDump to import files, you must UNCHECK the Extended Inserts option when exporting.




