[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2933?page=c...
]
Steve Ebersole updated HHH-2933:
--------------------------------
Assignee: Steve Ebersole
Description:
Introducing DialectResolver!
Much better approach to resolving JDBC Connection information to Dialect allowing users to
define custom behavior
was:
Currently the DialectFactory has the static attribute MAPPERS, that hold the dialects. If
the dialect is not found, Hibernate will throw an exception. There is already an TODO tag,
set for this.So, could this be possibly done, so that the values really are a) in a
properties file or b)additions could be made to the map programmaticaly by users.
This would be more flexible for advanced users, that work with experimental jdbc
drivers(that don't return a standard name for the database).
The current trunk version of DialectFactory:
// TODO : this is the stuff it'd be nice to move to a properties file or some other
easily user-editable place
private static final Map MAPPERS = new HashMap();
static {
MAPPERS.put( "HSQL Database Engine", new VersionInsensitiveMapper(
"org.hibernate.dialect.HSQLDialect" ) );
MAPPERS.put( "H2", new VersionInsensitiveMapper(
"org.hibernate.dialect.H2Dialect" ) );
MAPPERS.put( "MySQL", new VersionInsensitiveMapper(
"org.hibernate.dialect.MySQLDialect" ) );
etc.....
Fix Version/s: 3.4
3.3.x
3.2.x
Issue Type: Patch (was: Improvement)
Summary: externalize automatic resolution of Dialect (Tomoto Shimizu Washio)
(was: DialectFactory dialects should be in a properties file)
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