[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2933?page=c...
]
Steve Ebersole commented on HHH-2933:
-------------------------------------
Oh, and personally I'd rather not see SQLException being propogated. Guess it depends
on the nature of the exception; connection problems should indicate an immediate stop to
the processing, whereas others should equate to "this resolver does not handle this
connection" imo.
I'll take a look as i am applying the patches (already started).
externalize automatic resolution of Dialect (Tomoto Shimizu Washio)
-------------------------------------------------------------------
Key: HHH-2933
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2933
Project: Hibernate Core
Issue Type: Patch
Components: core
Affects Versions: 3.2.5
Reporter: Mikael Kopteff
Assignee: Steve Ebersole
Fix For: 3.2.x, 3.3.x, 3.4
Attachments: dialect_registration.zip, dialect_registration_rev2.zip
Introducing DialectResolver!
Much better approach to resolving JDBC Connection information to Dialect allowing users
to define custom behavior
--
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira