Comments on: On restoring a single table from mysqldump http://code.openark.org/blog/mysql/on-restoring-a-single-table-from-mysqldump Blog by Shlomi Noach Thu, 09 Sep 2010 18:52:58 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Vitaly http://code.openark.org/blog/mysql/on-restoring-a-single-table-from-mysqldump/comment-page-1#comment-17217 Vitaly Thu, 02 Sep 2010 11:00:21 +0000 http://code.openark.org/blog/?p=1630#comment-17217 Even it's not directly related to this topic, I noticed that if we cutting specific table dump from the whole DB dump there is a problem with restoring of TIMESTAMP fields - they become UTC instead of local time. adding /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */; /*!40103 SET TIME_ZONE='+00:00' */; (as we have in a dump produced by mysqldump) before table data fixes this problem. Regards, Vitaly Karasik Even it’s not directly related to this topic, I noticed that if we cutting specific table dump from the whole DB dump there is a problem with restoring of TIMESTAMP fields – they become UTC instead of local time.

adding

/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE=’+00:00′ */;

(as we have in a dump produced by mysqldump) before table data fixes this problem.

Regards,
Vitaly Karasik

]]> By: shlomi http://code.openark.org/blog/mysql/on-restoring-a-single-table-from-mysqldump/comment-page-1#comment-8111 shlomi Tue, 15 Dec 2009 13:31:30 +0000 http://code.openark.org/blog/?p=1630#comment-8111 @TVNshack sed can come in handy here, too. @TVNshack

sed can come in handy here, too.

]]> By: TVNshack http://code.openark.org/blog/mysql/on-restoring-a-single-table-from-mysqldump/comment-page-1#comment-8106 TVNshack Tue, 15 Dec 2009 11:15:39 +0000 http://code.openark.org/blog/?p=1630#comment-8106 Watchout the problem of the automatically generated AUTO_INCREMENT table option that mysqldump generates and that MATCH only with the INSERT statements that may come right after in the dump. Even if you specify a --no-data, that AUTO_INCREMENT=nnn table option will still appear. If you intend to create a table from that extracted definition and for which you may not want to insert the exact same data, LAST_INSERT_ID will not be adapted for the need of your empty table. Your table first row inserted relying on AUTO_INCREMENT column definition option will start with an offset AUTO_INCREMENT value. I would recommend to edit the mysqldump output to reset each AUTO_INCREMENT table option to AUTO_INCREMENT=1 and let the eventual INSERTs manage LAST_INSERT_ID (see bug #44425) Watchout the problem of the automatically generated AUTO_INCREMENT table option that mysqldump generates and that MATCH only with the INSERT statements that may come right after in the dump.

Even if you specify a –no-data, that AUTO_INCREMENT=nnn table option will still appear. If you intend to create a table from that extracted definition and for which you may not want to insert the exact same data, LAST_INSERT_ID will not be adapted for the need of your empty table. Your table first row inserted relying on AUTO_INCREMENT column definition option will start with an offset AUTO_INCREMENT value.

I would recommend to edit the mysqldump output to reset each AUTO_INCREMENT table option to AUTO_INCREMENT=1 and let the eventual INSERTs manage LAST_INSERT_ID

(see bug #44425)

]]> By: Log Buffer #171: a Carnival of the Vanities for DBAs | The Pythian Blog http://code.openark.org/blog/mysql/on-restoring-a-single-table-from-mysqldump/comment-page-1#comment-7693 Log Buffer #171: a Carnival of the Vanities for DBAs | The Pythian Blog Fri, 04 Dec 2009 18:05:02 +0000 http://code.openark.org/blog/?p=1630#comment-7693 [...] Noach shares his thoughts on restoring a single table from mysqldump. “Given a dump file (generated by mysqldump), how do you restore a single table, without [...] [...] Noach shares his thoughts on restoring a single table from mysqldump. “Given a dump file (generated by mysqldump), how do you restore a single table, without [...]

]]> By: Gavin Towey http://code.openark.org/blog/mysql/on-restoring-a-single-table-from-mysqldump/comment-page-1#comment-7584 Gavin Towey Thu, 03 Dec 2009 00:32:08 +0000 http://code.openark.org/blog/?p=1630#comment-7584 Nice! The sed only method is a good improvement. Nice! The sed only method is a good improvement.

]]> By: shlomi http://code.openark.org/blog/mysql/on-restoring-a-single-table-from-mysqldump/comment-page-1#comment-7482 shlomi Tue, 01 Dec 2009 21:02:27 +0000 http://code.openark.org/blog/?p=1630#comment-7482 @Chris Good! Credits due to gtowey Regards @Chris

Good! Credits due to gtowey

Regards

]]> By: WhirCat · restoring a single table from mysqldump http://code.openark.org/blog/mysql/on-restoring-a-single-table-from-mysqldump/comment-page-1#comment-7478 WhirCat · restoring a single table from mysqldump Tue, 01 Dec 2009 20:24:27 +0000 http://code.openark.org/blog/?p=1630#comment-7478 [...] via On restoring a single table from mysqldump | code.openark.org. [...] [...] via On restoring a single table from mysqldump | code.openark.org. [...]

]]> By: Chris http://code.openark.org/blog/mysql/on-restoring-a-single-table-from-mysqldump/comment-page-1#comment-7475 Chris Tue, 01 Dec 2009 19:14:50 +0000 http://code.openark.org/blog/?p=1630#comment-7475 I just used your method in my PROD environment and it is defiantly easier and more efficient than my method with grants. Again, thanks for the slick method. I just used your method in my PROD environment and it is defiantly easier and more efficient than my method with grants. Again, thanks for the slick method.

]]> By: Chris http://code.openark.org/blog/mysql/on-restoring-a-single-table-from-mysqldump/comment-page-1#comment-7469 Chris Tue, 01 Dec 2009 17:20:12 +0000 http://code.openark.org/blog/?p=1630#comment-7469 yet another great solution, thanks for the comparison and improvements! yet another great solution, thanks for the comparison and improvements!

]]>