We updated mariadb-java client from version 2.72 to 3.1.2
This seems to cause an jdbc compatibility problem as follows.
There is a Timestamp 0,0,0 0,0,0:000 in the database. mariadb-java reads this value and converts this to null.
I dont know what the comment means, and the link doesnt work for me. However this behavior means that ResultSet#getTimestamp will return null, if the databse value is not NULL but 0,0,0 0,0,0:000.
our codebase asumes that ResultSet#getTimespamp can only return null, if the Coloumn Value is SQL NULL (as checked with #wasNull). However in this case #wasNull will return false, yet the value will be null, causing a Nullpointer Exception in the process.
I guess thats a jdbc compatibility violation?