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
We have had situations where Hibernate uses null when all fields in a component are null, which isn't consistent with our desired approach. We can't fix it in Hibernate, so it would be nice if we could have Moo sort it out at translation time, by telling it that if a particular property is null, just instantiate an instance of the target class.
Not sure the right way to include that in the configuration/annotation, but something to think about.
The text was updated successfully, but these errors were encountered:
We have had situations where Hibernate uses null when all fields in a component are null, which isn't consistent with our desired approach. We can't fix it in Hibernate, so it would be nice if we could have Moo sort it out at translation time, by telling it that if a particular property is null, just instantiate an instance of the target class.
Not sure the right way to include that in the configuration/annotation, but something to think about.
The text was updated successfully, but these errors were encountered: