On 24/05/11 10:04, Brett Parker wrote:
Even with the "sensible" backend that does foreign keys and transactions, it still has serious issues if you want to change the schema - rather than, you know, adding a column it creates a whole new table, locks the database, does a copy from the old table in to the new, drops the old table and renames the new...
Now do that with a large dataset...
Do you have a reference for this?
I do have a project which will generate large datasets and was using InnoDB, so I ran some tests, and was able to continue inserting data into one table whilst modifying the schema of another. (Tested on MySQL 5.0.51a so not a very new release.)