Statement.getGeneratedKeys() returns a non-empty ResultSet if AUTO_INCREMENT was unaffected

How to reproduce:
Run test case GeneratedKeysTest.testGeneratedKeysInsertOnDuplicateUpdate() in the attached file GeneratedKeysTest.java. Psedo code:
1. Create a table with an AUTO_INCREMENT column.
2. Insert one row
3. Try to insert another row with the ON DUPLICATE KEY UPDATE syntax that updates the previous inserted row.

Actual:
This assert fails:
assertTrue(resultSet.next());

That is: the ResultSet is not empty, it contains one row with the value 0 for the first column. The value 0 is just a dummy value and does not reflect any value of the key.

Expected:
The Javadoc for Statement.getGeneratedKeys() says: “If this Statement object did not generate any keys, an empty ResultSet object is returned.”

Discussion:
I’m guessing that the INSERT ON DUPLICATE-feature is a Mysql specific extension to SQL. It is my option that the feature does not mix very with the Javadoc for Statement.getGeneratedKeys(). My recommendation to others would be to not write code that use this feature.

On the code I’m working on this feature is however used. We previously used Mysql JDBC driver and are now switching to MariaDB. My attached test case passes with Mysql JDBC driver (the ResultSet is empty). It would be good for me if MariaDB behaves the same.