[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6944?page=c...
]
Steve Ebersole commented on HHH-6944:
-------------------------------------
Or maybe we leave {{org.hibernate.dialect.Dialect#buildSQLExceptionConverter}} in place
and just add {{org.hibernate.dialect.Dialect#buildSQLExceptionConversionDelegate}},
converting our implementations from the former to the latter.
The idea of {{org.hibernate.dialect.Dialect#buildSQLExceptionConverter}} would be that if
the dialect returned any non-null value, we would use that without any other delegation.
Update Dialects to return SQLExceptionConversionDelegate
--------------------------------------------------------
Key: HHH-6944
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6944
Project: Hibernate Core
Issue Type: Improvement
Components: core
Affects Versions: 4.0.1
Reporter: Steve Ebersole
Assignee: Hardy Ferentschik
Fix For: 4.1.0
Currently dialects return a {{SQLExceptionConversion}} which takes on full responsibility
for conversion. I added {{SQLExceptionConversionDelegate}} to support a more
collaborative/chained approach. The idea is that eventually we would have just a single
{{SQLExceptionConversion}} (or maybe it becomes a class instead of interface) that
contains multiple {{SQLExceptionConversionDelegate}} instances to which it would
delegate.
The {{SQLExceptionConversionDelegate}} instances would be determined from:
# a "static" one based on the JDBC 4 defined {{SQLException}} hierarchy
# one for SQLState codes for either X/Open or SQL-2003 codes, depending on
{{java.sql.DatabaseMetaData#getSQLStateType}}
# vendor specific error code or SQLState interpretations via Dialect
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira