|
The server sends error code and SQL state for each error. Error code permits to identify the exact error (because error message can be internationalized), SQL state indicate the error category. Those categories permit to create the appropriate SQLException instance, like DataIntegrityViolationException.
The connector doesn't normally have to map error code but must rely on SQLState.
Error 1032 has an associate "HY000" error code that corresponds to generic kind of error, so the connector will throw a "basic" SQLException, a "23000" error would be an Integrity constraint violation error, then spring would throw DataIntegrityViolationException.
The correction would be on server side changing error the SQL state associate to error 1032 from 'HY000' to '23000'.
Could you explain why you think that error must be an integrity constraint violation (It doesn't seem to me to be this kind of error, but I'm no expert in this area).
Or better, directly create an issue server side (https://jira.mariadb.org/projects/MDEV/)
|