News for hackers. Stuff that matters.

A comment on Why The Clock is Ticking for MongoDB. Parent comment

Re:Why The Clock is Ticking for MongoDB by rsynnott on Thursday April 17, 2014 @10:01AM (#7603561)
> 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.

[ Parent | on HN ]
Re:Why The Clock is Ticking for MongoDB by neverminder on Thursday April 17, 2014 @10:32AM (#7603799)
I can confirm that is still the case with latest MySQL version, which is why my company is moving to PostgreSQL.
[ Parent | on HN ]
Re:Why The Clock is Ticking for MongoDB by leif on Thursday April 17, 2014 @11:06AM (#7604023)
You're wrong. 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.

[ Parent | on HN ]
Re:Why The Clock is Ticking for MongoDB by beberlei on Thursday April 17, 2014 @11:27AM (#7604164)
the mysql documentation definatly states otherwise: http://dev.mysql.com/doc/refman/5.7/en/innodb-create-index-o...
[ Parent | on HN ]
Re:Why The Clock is Ticking for MongoDB by emeraldd on Thursday April 17, 2014 @10:12AM (#7603633)
Was that InnoDB or MyISAM? I didn't realize it used the same technique on both.
[ Parent | on HN ]