Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
3.0.0, 3.0.3, 3.0.5, 3.1.0
-
Arch Linux, OpenJDK 18
Description
After upgrading the MariaDB Java connector in a web application from v2.7.5 to v3.1.0 one of the JUnit tests started failing. When the method 'executeBatch()' is called on a PreparedStatement, then it returns "SUCCESS_NO_INFO".
I have created a reproducible Java application, see attachment.
If this application is run with v2.7.7, then it returns an array of update counts.
If this application is run with v3.0.0 or newer (for example v3.1.0), then it returns "SUCCESS_NO_INFO".
To me this looks like a regression where v3.1.0 breaks backwards compatibility.
Please correct me if I am wrong.
Attachments
Issue Links
- duplicates
-
CONJ-920 MariaDB Java Client 3.0.3 - Java batched statements with optimistic locking failing
- Closed