]]>
Call us: 1-888-316-9775 • Contact Us
MySQL and InnoDB are trademarks of Oracle Corp.
Proudly running Percona Server
Copyright © 2006-2013 Percona Inc.
Copyright, Trademark, and Privacy Policy • Sitemap
]]>
Differences
This shows you the differences between two versions of the page.
|
ptdev:blueprints:redesign-pt-online-schema-change [2012/03/28 20:51] daniel.nichter [Redesign pt-online-schema-change] |
ptdev:blueprints:redesign-pt-online-schema-change [2012/03/29 16:47] (current) baron |
||
|---|---|---|---|
| Line 50: | Line 50: | ||
| - (DONE) Make the tool use unique trigger names so that multiple tools can work on several tables at once. Choose trigger names based on the table name. Don't do leading underscores strategy; that is unnecessary because it would only happen if two alters were happening on the same table at once. | - (DONE) Make the tool use unique trigger names so that multiple tools can work on several tables at once. Choose trigger names based on the table name. Don't do leading underscores strategy; that is unnecessary because it would only happen if two alters were happening on the same table at once. | ||
| - (DONE) If the tool cancels or exits without cleaning up triggers and temp tables (for example a CTRL-C, which we would hopefully want to resume in a future version), print out the DROP syntax for the triggers and temp table it left behind. (In other words: always clean up unless the tool was interrupted, in which case, leave stuff so it can be resumed, but print the SQL to clean up.) | - (DONE) If the tool cancels or exits without cleaning up triggers and temp tables (for example a CTRL-C, which we would hopefully want to resume in a future version), print out the DROP syntax for the triggers and temp table it left behind. (In other words: always clean up unless the tool was interrupted, in which case, leave stuff so it can be resumed, but print the SQL to clean up.) | ||
| + | - After the tool finishes, use SHOW TABLES and SHOW TRIGGERS to verify that all of the _new and _old tables and triggers are really gone. For example, if the tool creates sakila._actor_new and then renames to actor and _actor_old, verify that actor exists, and that _actor_new and _actor_old don't. Verify that actor doesn't have triggers. Notify the user of anything that's unexpected. | ||
| ===== Daniel's notes ===== | ===== Daniel's notes ===== | ||
Except where otherwise noted, content on this wiki is licensed under the following license:CC Attribution-Noncommercial-Share Alike 3.0 Unported
