Commit

141e3c6

A MariaDB 11.4 dump failed on every CREATE when I loaded it into MySQL 8.4. So I had Schemity write the MySQL version instead. Schemity is the desktop database design software I build. In the next release it reads MariaDB as its own database and writes its schema for MySQL: UUID becomes CHAR(36), INET6 becomes VARCHAR(45), and the uca1400 collation MySQL has never had is dropped. The script ran on MySQL 8.4.11 with no errors. Three tables, both foreign keys. What it could not translate sits in a list at the top of the script. The invoice number lost its default, because MySQL has no sequences, and now needs its value from the application. That list is the real migration.

commit 141e3c6

We were utilizing MariaDB with ServiceNow but they migrated us off to a new provider so thankfully we didn't have this issue. I could only imageine the headache we would be facing if we had this issue.