http://wanderr.com/jay/mysql-atomic-rename-fk-constraints-oops/2008/11/17/ Rantings of a Grooveshark Developer Wed, 21 Sep 2011 10:35:10 +0000 hourly 1 http://wordpress.org/?v=3.1.3 http://wanderr.com/jay/mysql-atomic-rename-fk-constraints-oops/2008/11/17/comment-page-1/#comment-2453 Jay Tue, 30 Aug 2011 09:15:36 +0000 http://wanderr.com/jay/?p=121#comment-2453 We've used this in a production environment where if it was not atomic, things would have crashed and burned, and they did not, so yes I'm pretty sure. :) We’ve used this in a production environment where if it was not atomic, things would have crashed and burned, and they did not, so yes I’m pretty sure. :)

]]> http://wanderr.com/jay/mysql-atomic-rename-fk-constraints-oops/2008/11/17/comment-page-1/#comment-2375 Giannis Mon, 11 Jul 2011 15:05:11 +0000 http://wanderr.com/jay/?p=121#comment-2375 Are you sure "RENAME TABLE CurrentTable TO OldTable, NewTable TO CurrentTable" is really atomic? I've read the related documentation (12.1.20) which states that "The rename operation is done atomically,..." but it doesn't clearly state if the whole statement (with multiple renames) is executed atomically, or if the atomicity is per single table-rename (so each table rename is atomic, but all of them are not). I would really like to have this clarified. Thanks. Are you sure “RENAME TABLE CurrentTable TO OldTable, NewTable TO CurrentTable” is really atomic? I’ve read the related documentation (12.1.20) which states that “The rename operation is done atomically,…” but it doesn’t clearly state if the whole statement (with multiple renames) is executed atomically, or if the atomicity is per single table-rename (so each table rename is atomic, but all of them are not). I would really like to have this clarified. Thanks.

]]>