You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My knee-jerk would be an inner class of Book_, something like Book_.Id_ which does not collide with anything currently defined in 5.1.1. But it does have one potential problem in that in Hibernate Processor, IIRC, we have started using the convention X_.Y_ when you have a static inner class annotated @Entity (which is permitted by the spec, but currently not considered in 5.1.1). Right, @cigaly?
@gavinking Actually, what I've done was generating separate class file for each (static) inner class, so that X.Y will produce X_Y_. [But there should be not big problem to make it as inner class X_.Y_]
Why not generate something like Book_.Id [or Book_Id] by simply ommiting underscore at the end, so that distinction will be more clear?
Given an entity meets:
@IdClass
annotatedFor example:
It would be convenient if a record class is generated as implicit
@IdClass
candidate names of generated record class:
The text was updated successfully, but these errors were encountered: