By V I R U S on
Hello Drupal Community!
Today i noticed on MySQL page, in products list some strange thing. It seems, that Oracle will take out the InnoDB from the free version of MySQL.
Since Drupal uses InnoDB, that's not that good as it could be.
Prooflink: http://www.mysql.com/products/
Are you ready to pay 2000$?
Comments
Community Edition
Seems the table conveniently misses off the GPL Community Edition http://www.readwriteweb.com/cloud/2010/11/oracle-drops-innodb-from-mysql... and http://dev.mysql.com/downloads/mysql/ which continues to have innodb.
Still nothing of a surprise given Oracle's orientation to Free Software.
ReadWriteWeb says it won't
ReadWriteWeb says it won't affect the community edition of MySQL:
http://www.readwriteweb.com/cloud/2010/11/oracle-drops-innodb-from-mysql...
better than $2000
Are you ready to use mariadb?
It's faster anyway.
--
Morris Animal Foundation
Community mySQL keeping InnoDB
According to http://www.mysql.com/products/community/ the community version still supports InnoDB. They just didn't list the community edition on the chart.
I don't think Oracle will mess with it, either. People would start switching away overnight, and while that might not directly cut into their income, the ubiquity of mySQL community edition is one of the big selling points for their paid versions. A mass migration from mySQL to, say, Postgre would cut that off at the knees, so Oracle has a solid financial motive for making sure the free version remains fully functional and anatomically correct. (Sorry, Star Trek/Voltaire reference.)
In the unlikely event that Oracle did try to shoot themselves in the foot by making with (as the LOLcats would say) "teh eebols," I still wouldn't worry about our beloved CMS. I mean, sure, the main focus of Drupal development has been with mySQL, but it supports other databases, and I've no doubt that if worse came to worst, our heroic developers would have rock-solid migration solutions out there before most people even knew they were needed.