10 years is more than long enough for users to be fully WARNed

This commit is contained in:
Gavin King 2024-03-23 22:28:30 +01:00
parent d3357fe719
commit 77916c8304
2 changed files with 0 additions and 16 deletions

View File

@ -1032,12 +1032,6 @@ public class EntityBinder {
if ( ignore ) { if ( ignore ) {
LOG.debugf( "Ignoring explicit @DiscriminatorColumn annotation on: %s", annotatedClass.getName() ); LOG.debugf( "Ignoring explicit @DiscriminatorColumn annotation on: %s", annotatedClass.getName() );
} }
else {
LOG.applyingExplicitDiscriminatorColumnForJoined(
annotatedClass.getName(),
AvailableSettings.IGNORE_EXPLICIT_DISCRIMINATOR_COLUMNS_FOR_JOINED_SUBCLASS
);
}
return !ignore; return !ignore;
} }
else { else {

View File

@ -1594,16 +1594,6 @@ public interface CoreMessageLogger extends BasicLogger {
@Message(value = "Named parameters are used for a callable statement, but database metadata indicates named parameters are not supported.", id = 456) @Message(value = "Named parameters are used for a callable statement, but database metadata indicates named parameters are not supported.", id = 456)
void unsupportedNamedParameters(); void unsupportedNamedParameters();
@LogMessage(level = WARN)
@Message(
id = 457,
value = "Joined inheritance hierarchy [%1$s] defined explicit @DiscriminatorColumn. Legacy Hibernate behavior " +
"was to ignore the @DiscriminatorColumn. However, as part of issue HHH-6911 we now apply the " +
"explicit @DiscriminatorColumn. If you would prefer the legacy behavior, enable the `%2$s` setting " +
"(%2$s=true)"
)
void applyingExplicitDiscriminatorColumnForJoined(String className, String overrideSetting);
// 458-466 reserved for use by main branch (ORM 5.0.0) // 458-466 reserved for use by main branch (ORM 5.0.0)
@LogMessage(level = DEBUG) @LogMessage(level = DEBUG)