Fix problem that SqlGrammarException is not catched with MySQL 5.7

[thomaslow]

See issue #5563

[solth]

@m-kotzyba can you confirm that the change in this pull request resolves the issue for you with a MySQL 5.7 database, too?

[m-kotzyba]

@solth Unfortunately, I can't make any statement on this, i.e., neither confirm nor deny. The update of our Kitodo and system in general (including MySQL) was the first choice for various reasons.

[solth]

@thomaslow please rebase against the current master as your PR is the next merge candidate

[thomaslow]

@solth Github doesn't report any merge conflicts to me. Not sure what I am supposed to do.

[solth]

@thomaslow Github only reports syntactic conflicts, but not semantic problems. We had multiple occassions where no merge conflicts would be reported between an - outdated - branch and the master branch and the corresponding pull request passed all automatic checks (Codacy, automatic tests etc.). After merging the pull request, though, the resulting code would fail at some new test in the master branch because the tested functionality was changed by the pull request.

So basically just rebase your branch against the current master or merge the current master into you branch to update it and verify that all automatic checks pass.

[thomaslow]

@solth FYI, there is a new beta feature in GitHub that should help you with merging by automatically re-running actions before merging: merge queues.

[solth]

FYI, there is a new beta feature in GitHub that should help you with merging by automatically re-running actions before merging: merge queues.

@thomaslow thanks alot for the hint. @henning-gerhardt already suggested this new Github feature to me, I just haven't gotten around to activate and configure it, yet!

@subhhwendt & @joerg-liebenow could you approve this PR once you successfully tested the branch with your test system with MySQL 5.7 database?

[solth]

Tested and can confirm that the change fixes the linked issue.