Add new indexes when updating log table schema regardless of engine change
While working on at.greenpeace.advancedlogtables, I noticed that the
System.updatelogtables API call only adds new indexes set by the
alterLogTables hook when it's accompanied by an engine change.
That's generally fine when the indexes don't change, but once new ones are added you'd have to temporarily change the engine or apply the new ones manually.
Is there a particular reason why we'd want to keep that behaviour, or can we change it so that new indexes are added regardless of the engine?
I have a patch ready for this, but wanted to check if there's agreement on this first.