Closed kehh closed 1 year ago
(to be clear, this is after all current Providence database migrations up to 185 have been run on these databases.)
can confirm I noticed this on our applications too, asked a question about it on gitter (Apr 26)
Looking through this there are four categories of misalignment:
alter table ca_sql_search_word_index modify index_id bigint unsigned auto_increment
, which is meant to prevent very large indexes from failing due to exhaustion of index keys. It was not pushed in a migration because changing the size of the key will trigger a really lengthy rebuild of the table, and in 10+ years we've only seen one system that needed it. I'd still hold this one back, but the others should be fixed.I'm most of the way through a migration script to try and resolve these. We've just gotten bitten by the bigint issue on one system which is what led me here. Will send a PR a bit later this evening.
I'll do the bigint and UTFmb4 fixes in a separate migration tool if you don't want them in providence.
The utfmb4 and search index binging changes should not be done as migrations.
I've just run a database diff tool over an older providence install and a current install. It looks like a fairly large diff. A bunch of them relate to changing tables utf8mb4 and changing names of indexes. However there are other changes like data type changes (bigint vs int on ca_sql_search_word_index.index_id) which have consequences for the operation of the system.
I'm going to put them here but will try to wrap this up in a database migration - let me know if you want this all in one block or multiple migrations: