@josephbuchma Oh, I can't quite remember the details, sorry. Maybe it was due to a missing &multiStatements=true in the connection string (see here), but I'm not sure. Just skimmed the related commit on our side, but there are no details, I'm afraid.
I have some inconsistent results when applying migrations. I tracked it down to
GET_LOCK
sometimes returningfalse
.First, I created one migration which sets up all the initial tables. That failed (well, tables are correctly set up, but there is an error returned):
Next, I simply removed the last table create statement and put it into a 2nd migration. That worked:
Okay, I thought, maybe a single migration file turns out to be a problem. But no, if I create all tables in separate migration files, it fails again:
I tried to extract a reproducible test, but I couldn't reproduce it yet in a test case.
BTW: I'm using MariaDB from homebrew.
Do you have any idea why this might happen? Does this look somehow familiar to you?