3 ms·
> In most databases, altering a schema is an operation that's over quickly I think many people were burned by MySQL InnoDB, which modifies (or modified; I'm st
by rsynnott 13y ago
> In most databases, altering a schema is an operation that's over quickly
I think many people were burned by MySQL InnoDB, which modifies (or modified; I'm still on quite an old version) schemas by making a new table and copying the data, and don't realise that all databases don't do that.
- emeraldd 13y agoWas that InnoDB or MyISAM? I didn't realize it used the same technique on both.
- neverminder 13y agoI can confirm that is still the case with latest MySQL version, which is why my company is moving to PostgreSQL.
- leif 13y agoYou're wrong. http://dev.mysql.com/doc/refman/5.6/en/innodb-create-index-overview.html http://dev.mysql.com/doc/refman/5.6/en/innodb-create-index-o... InnoDB tables have online, non-copying (for most operations) DDL in 5.6. Also, TokuDB has had online, non-copying DDL (column add and drop, add index) since TokuDB 5.0.
- beberlei 13y agothe mysql documentation definatly states otherwise: http://dev.mysql.com/doc/refman/5.7/en/innodb-create-index-overview.html http://dev.mysql.com/doc/refman/5.7/en/innodb-create-index-o...