Unlike MySQL, the WKT-input spatial analysis functions inMariaDB likeST_GeomFromText andST_DISTANCE do not take an options parameter:https://mariadb.com/kb/en/st_geomfromtext/

If I understand correctly, we need to pass "axis-order=long-lat" because otherwise some versions of MySQL will interpret coordinate pairs as lat-long. For MariaDB, this is not necessary because MariaDB reads WKT values as long-lat by default.

In its current state, using this package with MariaDB will throw the following exception when trying to insert or update values for a spatial column, because we force the third options parameter inST_GeomFromText:

Syntax error or access violation: 1582 Incorrect parameter count in the call to native function 'ST_GeomFromText'

This is because the MariaDB function expects at most two arguments:https://github.com/MariaDB/server/blob/cf87f3e08c10dd7a944447ddee93fbc3827e6570/sql/item_geofunc.cc#L2993

This PR adds the option to set a$wktOptions property on the model that will overwrite the default options "axis-order=long-lat". It can be set to false to remove the options parameter entirely, which fixes the errors when using MariaDB.

Additionally, it adds flexibility for users that may want or need to change the WKT options for whichever reason.

This is completely backwards-compatible, because if$wktOptions is not set, it will default to "axis-order=long-lat".