I know that MariaDB is not stated as officially supported by this gem, so feel free to close this as unrelated.

During the update of this gem in of my applications I noticed that locks did not work anymore and with_advisory_lock return false. After some digging I found that since version 7 the gem uses MySQL's native way of setting a timeout by passing -1 to the GET_LOCK function. Sadly this does not seem to be supported by MariaDB. Would it be possible to use the Ruby level timeout instead for MariaDB databases or default to the maximum value for the GET_LOCK function instead?

On the other hand I feel like setting a timeout should be encouraged anyway so maybe I should just set one but the behavior still felt a bit unexpected as many people use MariaDB as a replacement for MySQL.