This is a bit of a problem with Hibernate's JDBCException class: It stores context such as the SQL String but doesn't include it in the exception message As a consequence, I've added that context explicitly when translating those exceptions: directly, without adding another exception to the chain.
14. The DataAccessException seems to be ignored after leaving dao area. And that's a good thing! Let it fly down through the whole stack. You probably have transactions on service layer - the exception will transparently cause the outermost transaction to be rolled-back. Great! Now it will find its way to the controller.
I have the below entity where the deleted column in database is of type character with expected values 'Y' or 'N'. I'm using the YesNoConverter to encode the boolean value as 'Y' or 'N' . public class User { @Id @GeneratedValue(strategy = GenerationType.IDENTITY) private Long id; . .
.jdbc exception on hibernate data access
