[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2933?page=c...
]
Tomoto Shimizu Washio commented on HHH-2933:
--------------------------------------------
Thank you to elaborate. I understand your intention.
DatabaseMetaData in the parameter is great, yeah!
I agree it would make sense avoiding SQLException to clearly show the intent and enforce
the implementors to do what they should do. I was a little afraid that it might impose
unnecessary exception handling on the resolvers, but now I think it would not be much a
problem because they could still extend SimpleDialectResolver in order not to be bothered
by SQLException if they needed only the very basic information such as database name.
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