MariaDB: Make version check compatible with 10.10

[lastzero]

The system variable innodb_version is missing in MariaDB 10.10, unclear if accidentally or intentionally. Since this causes an error in the MariaDB version check, we must assume that it is a compatible release. In all other releases down to MySQL 8 this variable is set to the plain version (without additions like the application name or distribution which could cause parse errors).

[lastzero]

This fix has been released, a new stable build will be available soon:

• https://docs.photoprism.app/release-notes/#november-18-2022

Note that MariaDB 10.10.2 has only been released yesterday. Since we can't see into the future, reacting this fast is the best we can do in case something unexpectedly changes in a new MariaDB version.

We recommend that you check compatibility before you upgrade to a brand new MariaDB version and don't use the latest tag.

[lastzero]

We have updated our documentation for you to clarify which versions are supported and what the best upgrade strategy is:

Our configuration examples are usually based on the current stable version to take advantage of performance improvements. This does not mean that older versions are no longer supported and you must upgrade immediately.

Since it is possible that new major versions of MariaDB require changes in PhotoPrism to be compatible, you should check compatibility before upgrading to new MariaDB versions that have been released very recently. We therefore recommend not using the :latest tag for the Docker image and to upgrade manually by changing the tag e.g. from :10.8 to :10.9 once we had the chance to test the new release:

services:
  mariadb:
    image: mariadb:10.9
    ...