Msg#: 4323526 posted 7:06 pm on Jun 9, 2011 (gmt 0)
Something to watch out for when doing exports from PHPMYADMIN is to set the "Maximal length of created query" to something really really high. I have reached the default limit a couple times and it has messed up the export.
Msg#: 4323526 posted 4:56 pm on Jun 13, 2011 (gmt 0)
I don't know. The question is why you'd need to do it on selected tables. If you're moving a database, it should be easy - export entire database in an .sql dump, create new DB on new site, import new .sql file, done. If you're getting errors, I'd solve the problem, not make more work by doing individual tables.
At any rate, you can edit an .sql file like any other text file and add your own commands. It's really just a batch file. An example, for one table,
DROP TABLE IF EXISTS `your-table-name`; CREATE TABLE IF NOT EXISTS `your-table-name` ( `id` int(10) unsigned NOT NULL auto_increment, `target` varchar(100) NOT NULL default '', `field_1` varchar(100) NOT NULL', `field_2` tinyint(2) NOT NULL default 0 ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1;
Msg#: 4323526 posted 1:11 pm on Jun 20, 2011 (gmt 0)
The question is why you'd need to do it on selected tables.
I knew there was more than one way of transferring WP blog onto another server (same domain).
I opted for export from within WP, and installed plugins manually.
The only leftover was data from statistics plugin. It was few more tables within existing WP database. That was what I ended up exporting each table record separately, and wondered why MySQL would complain when I tried to import (and overwrite) whole tables.