[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-1599) ConstraintViolationException returns null with PostgresDialect (Solution included)

Benoit Goudreault-Emond (JIRA) noreply at atlassian.com
Tue Jan 9 16:50:44 EST 2007


     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1599?page=all ]

Benoit Goudreault-Emond updated HHH-1599:
-----------------------------------------

    Attachment: HHH-1599-postgres-only.patch

Here is a version of the patch that does not change the other dialects.

> ConstraintViolationException returns null with PostgresDialect (Solution included)
> ----------------------------------------------------------------------------------
>
>          Key: HHH-1599
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1599
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.1.3
>  Environment: Hibernate 3.1.3 , Postgres 8.1.2 (i686), postgresql-8.2dev-501.jdbc.jar
>     Reporter: Niclas Lindberg
>     Priority: Minor
>  Attachments: HHH-1599-postgres-only.patch, HHH-1599.patch
>
> Original Estimate: 3 minutes
>         Remaining: 3 minutes
>
> ConstraintViolationException.getConstraintName() returns null. The problem is that the message being parsed comes from the SqlException that is the inputparameter to extractConstraintName(SqlException) in ViolatedConstraintNameExtracter. 
> Solution. The message provided by sqlException.getMessage() is "batch bla bla something" but the correct Exception message to parse is sqlException.getNextException().getMessage()

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira




More information about the hibernate-issues mailing list