[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-7059) The DerbyDialect deprecation warning should appear no more, when using one of the version-specific dialects
Guenther Demetz (JIRA)
noreply at atlassian.com
Thu May 3 08:06:49 EDT 2012
[ https://hibernate.onjira.com/browse/HHH-7059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46491#comment-46491 ]
Guenther Demetz commented on HHH-7059:
--------------------------------------
Pull request https://github.com/hibernate/hibernate-orm/pull/327
> The DerbyDialect deprecation warning should appear no more, when using one of the version-specific dialects
> ------------------------------------------------------------------------------------------------------------
>
> Key: HHH-7059
> URL: https://hibernate.onjira.com/browse/HHH-7059
> Project: Hibernate ORM
> Issue Type: Improvement
> Components: core
> Affects Versions: 4.0.1, 4.1.0
> Reporter: Guenther Demetz
> Priority: Minor
> Labels: derby
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Althoug setting a version=specific derby dialect
> config.setProperty("hibernate.dialect","org.hibernate.dialect.DerbyTenSevenDialect");
> following warning log appears:
> @LogMessage(level = WARN)
> @Message(value = "The DerbyDialect dialect has been deprecated; use one of the version-specific dialects instead",
> id = 430)
> This is because currently all versioned DerbyDialects are extending from deprecated super class DerbyDialect
> and the constructor of the super class does produce this warning logging regardsless of which concrete type the dialect is.
> public DerbyDialect() {
> super();
> LOG.deprecatedDerbyDialect();
> ...
> }
> Please see also:
> https://forum.hibernate.org/viewtopic.php?t=1014416
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list