ci: test against MariaDB 11.8 (latest LTS)

[joshtrichards]

• Resolves: #

Summary

https://mariadb.com/docs/release-notes/mariadb-community-server-release-notes/mariadb-11-8-series/what-is-mariadb-118
https://endoflife.date/mariadb

I suspect we can probably drop 10.3 finally for real since Ubuntu 20.04 is EoL, but leaving in for now.

TODO

• ...

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[provokateurin]

@joshtrichards the docs also need to be updated.

[nickvergessen]

While server works, not all apps work.

• Ref [Bug]: MariaDB 11.7.2 causing SQL error with not null longtext column (recognize app) #51596 and Testing against MariaDB 11.8 for https://github.com/nextcloud/server/… recognize#1295

I think we first need to figure out if that is something we need to fix in our migrations code or recognize app is doing something wrong.

[susnux]

Makes sense to at least add latest LTS to server CI

[susnux]

I think we first need to figure out if that is something we need to fix in our migrations code or recognize app is doing something wrong.

Before we add it to the documentation, stating it as supported, yes.
But we should already add the latest LTS to our CI pipeline.

[nickvergessen]

Recognize mystery is solved. It has a column vector which is a reserved keyword starting 11.7, so we are good to proceed here.

[susnux]

Recognize mystery is solved. It has a column vector which is a reserved keyword starting 11.7, so we are good to proceed here.

so this is a upstream bug, doctrine dbal needs to add this to their keywords to automatically quote it.
For dbal 5 this will be fixed automatically as it will quote everything possible (and will break your DB if you do the wrong casing ;) )