silverstripe/sapphire — comment on commit 6bf3f7ded400c925dd66df2c2612c095d447c7b0
File:  line 0
By chillu:

@sminnee @simonwelsh Awesome you've got that in, yay for using less deprecated APIs in SilverStripe :) This should also be tagged "API CHANGE". But more importantly: Let's try to document these relatively high impact changes at the time of commit, rather than release. Thats why we have /docs in source control now. So in a new /docs/en/changelog/alpha/3.0.0-alpha1.md file, write down an upgrading guide.

For example, what the "create table" changes mean for existing and new users and existing databases. What happens when you upgrade from 2.4 with an existing database, and then create a new subclass - will the new table(s) be in InnoDB, and everything else in MyISAM, hence potentially breaking any usage of MySQL FULLTEXT searches?

We should also create a script for migrating all tables to InnoDB, and explain why and when its a good idea (or point to a tech article that does it).