I think we should avoid a blanket statement of "no db changes except for major revisions" and instead opt for a concensus on changes. It may be that a database change is warranted (to fix a particularly grievious bug) in a minor version change.
As in this case, the change is not warranted for immediate release. Still, we may want to publish an Advisory to the wiki. Here we should add a note to the MySql page that users of MySql 5 will want to run a migration script and possibly replace some code (include as attachments). And add a note to the bug report pointing to the Advisory. That is all to say that we as a group should weigh any proposed db change and in which future release it should be included. The goal being to reduce the amount of work when upgrading to a new release. Lance
