Message Title

Steve Ebersole commented on an issue

Because the problem is that DatabaseInfoDialectResolver is not always enough information. DatabaseInfoDialectResolver is passed information about the database, not the driver. There are times (our own DataDirectOracle9Dialect e.g.) when you really need to select a Dialect based on driver info.

In terms of schema generation, "database info" is always enough. Where this can be problem is runtime.

Add Comment

Hibernate ORM /

HHH-8561

The problem is both {{DialectResolverInitiator}} and {{DatabaseInfoDialectResolverInitiator}}:
# use this setting, but expect different interface impls
# are enabled

Which leads to CCE problems in one or the other.

{{DialectResolverInitiator}} should go away and {{DatabaseInfoDialectResolverInitiator}} should interpret hibernate.dialect_resolvers as...

This message was sent by Atlassian JIRA