[MDEV-32109] Compatibility Broken with Mysql JDBC Connector Created: 2023-09-06  Updated: 2023-09-06  Resolved: 2023-09-06

Status: Closed
Project: MariaDB Server
Component/s: N/A
Affects Version/s: 11.0.3
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Nikhil Dabhade Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MDEV-31576 Unknown system variable 'transaction_... Closed
Relates
relates to MDEV-21921 Make transaction_isolation into a sys... Closed

 Description   

The MySQL JDBC connector/driver (version 8.0.32) is encountering an issue when trying to connect to MariaDB 11.0.3, resulting in an error message stating "Unknown system variable 'transaction_isolation'".

It appears that this error is related to the fact that 'transaction_isolation' has become a system variable in MariaDB 11.1.1, as indicated in MDEV-21921.

Interestingly, the MySQL JDBC connector can establish a connection with MariaDB 10.11.5, even though 'transaction_isolation' is not a recognized system variable in that version.

This suggests a potential bug or compatibility issue in MariaDB 11.0.3.



 Comments   
Comment by Daniel Black [ 2023-09-06 ]

In short, we didn't follow MySQL's changing of variable name to maintain compatibility with MySQL's Connector/J which changed to be compatible with MySQL-8.0.

As MariaDB compatibility isn't a major consideration there is a major version gap of 11.0 where it is incompatible and as you see, 11.1 is might be back if nothing else changes on the MySQL Connector/J side.

MariaDB Corporation does maintain a Connector/J that is compatible with MariaDB (and MySQL as we put in the effort - CONJ-604).

Like the user in MDEV-31576 I hope that a simple replacement of Connector/J implementation will resolve this error and support your applications reliably and with the quality and performance you get from MariaDB Server.

Generated at Thu Feb 08 10:28:54 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.