Allow mariadb to work with 10.3.x and up

[stronk7]

In #25 we unpinned mariadb back to 10... (right now pointing to 10.3.x)... just to discover that there are some config variables not existing anymore:

2019-01-18 22:25:48 0 [ERROR] mysqld: unknown variable 'innodb_file_format=barracuda'
2019-01-18 22:25:48 0 [ERROR] Aborting

Preventing the server to startup. So we pinned it back to 10.2.

This issue is about to try mariadb compatible with all the versions. Then we'll be really able to unpin it completely.

Ciao :-)

[deer667]

In MariaDB 10.2.2 and later, the default file format is Barracuda and Antelope is deprecated.

The config var can be removed and never verison of MariaDB can be pinned.

[scara]

Hi @deer667,
could you provide a ref for your statement?

I tried both https://mariadb.com/kb/en/mariadb-1022-release-notes/ and https://mariadb.com/kb/en/mariadb-1022-changelog/ w/o success.

Edit: Found it in https://mariadb.com/kb/en/innodb-system-variables/#innodb_file_format via #134:

• Default Value:
  • Barracuda (>= MariaDB 10.2.2)
  • Antelope (<= MariaDB 10.2.1)
• Valid Values: Antelope, Barracuda
• Deprecated: MariaDB 10.2
• Removed: MariaDB 10.3.1
• Re-introduced: MariaDB 10.4.3 (for compatibility purposes)
• Removed: MariaDB 10.6.0

Similar situation for https://mariadb.com/kb/en/innodb-system-variables/#innodb_large_prefix.

TIA,
Matteo

[stronk7]

Fixed by #134, so far, closing.