Picked up _JAVA_OPTIONS: -Xms128m -Xmx256m ================================================= Bug description: When we switched from MariaDB 10.1.16 server to Maridb 10.3.11, the behavior of MariaDB batch update processing behavior changed from non-atomic insert to atomic insert. This is an upward compatability issue for us. In this repro, we attempt to insert a block of 3 rows, one of which has a duplicate primary key value. With MaraiaDB server 10.1.16, the non-duplicate rows of a block insert would be inserted up to the first error. With MariaDB server 10.3.11, no rows are inserted and we don't know which row of the block caused the error,so we cannot attempt to insert all non-error rows. This looks like a bug. Is there a setting to restore the original behavior? ================================================= Registering Driver. Making a connection to: jdbc:mariadb://lnxx64r7:3308/db999_lnxx64r7 Connection successful. MariaDB JDBC driver version: 2.2.3 MariaDB DBMS version: 10.3.11-MariaDB-log con.createStatement() DROP TABLE TESTT CREATE TABLE TESTT(I1 INTEGER NOT NULL, I2 INTEGER NOT NULL, PRIMARY KEY (I1)) preparing: INSERT INTO TESTT (I1, I2) VALUES (?, ?) Setting parameter values for batch insert of 3 rows pstmt.setInt(1,1) pstmt.setInt(2,1) pstmt.addBatch pstmt.setInt(1,2) pstmt.setInt(2,2) pstmt.addBatch pstmt.setInt(1,1) pstmt.setInt(2,1) pstmt.addBatch executing batch insert: INSERT INTO TESTT (I1, I2) VALUES (?, ?) BatchUpdateException: java.sql.BatchUpdateException: (conn=2664) Duplicate entry '1' for key 'PRIMARY' Executing BatchUpdateException.getUpdateCounts() updateCounts.length = 3 updateCounts[0] = -3 updateCounts[1] = -3 updateCounts[2] = -3 count of successfully inserted rows = 0 preparing: SELECT COUNT(*) FROM TESTT executing: SELECT COUNT(*) FROM TESTT rst.next() returned true COUNT(*) 0 preparing: SELECT * FROM TESTT executing: SELECT * FROM TESTT rst.next() returned true I1,I2