Illegal fetch size when using most recent MariaDB driver

[Wooza]

Using setFetchSize(Integer.MIN_VALUE) (introduced by #56) is not allowed according to the documentation of setFetchSize:

It seems that older MariaDB drivers (<3.x.x) accepted Integer.MIN_VALUE for compatibility reasons, however the new major driver version was apparently rewritten from scratch to closely follow the JDBC specs and thus raises an exception when called with Integer.MIN_VALUE.

According to the documentation the proper solution is to use setFetchSize(1). My current workaround is to stick with the older driver but I would really like to update.

[rbygrave]

Do you want to submit a PR that bumps the jdbc driver the tests are using for MariaDB ? (that will then reproduce the problem)