On Wed, Nov 25, 2009 at 05:42:34PM -0500, Jay Pipes wrote: > [1] I'm still questioning whether this behaviour (of renaming > multiple tables) is actually atomic after looking through the code. > What the code ensures is that if one of the tables is not renamed > properly, all the tables will have their original names restored. > However, because there is no transactional state to this SQL > statement, if the power cuts out halfway through the operation to > rename a list of tables, I see nothing in the code which would > recover the original table names on a restart of the server. So, > it's kind of a "phony" atomicity since it is not guaranteed to be > consistent or durable.
If the power is cut you get to keep *all* the pieces! We need to have DDL in transactions and have engines knowledgable of this (i.e. allow multiple DDL ops in a transaction) and be Durable to failure during DDL transactions. The only engines I know of that have this capability are InnoDB and NDB... and only in the Embedded InnoDB API... so really, just NDB. -- Stewart Smith _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
