I'm having issues with SQLStateConverter because in some database installations that raise error messages in other languages other than english, SQLStateConverter creates ConstraintViolationException with null contraint name. Specifically in my case I'm using a PostgreSQL database installation in English and all is working fine but when I test my application in an PostgreSQL Database installed on Spanish I get null contraint names.

I digg a little about this and the problem is with templates in TemplatedViolatedConstraintNameExtracter implementation peer Dialect, where the template is hand writed for extract constraint names from English errors messages that came from the Database.

I think that this is a bug, but before I create an issue on Jira I want to know if it can be resolved in any way. PostgreSQL has a configuration value to raise localized error messages but what about legacy databases that store data for already running systems on the same server?