Hi,
We recently had this issue opened about us not choosing the right access
type for a mapped super class:
https://hibernate.atlassian.net/browse/HHH-12938 .
Hibernate currently base the access type decision on the sole placement of
the @Id annotation, which, in the case of a @MappedSuperclass m
I disagree that logging a single message is a better solution because that
probably ends up wrapping multiple lines, just as your sample happened to
do in the email. IMO that is actually more difficult to read.
And I just do not understand this idea that we have to direct people to
enable logging
Pretty good idea but definitely too much work for the effort I want to put
in it right now.
But, yes, we can do that for version 7.0.1.Final, I like your example :).
I will make a proposal to reduce the log verbosity (enhanced classes,
hibernate.properties missing and a few others) but keep the i
+1 to polish output, but:
I don't want to need to figure out how to reconfigure whatever Logger
of the day one happens to hit, to finally notice that essential
configuration details are wrong. Mostly because it requires to get the
idea to actually check this, which is not a straightforward thought
