I think it was since Hibernate 4 that this "protection" was created that makes Hibernate throw this exception in various situation on ManyToOne associations. AFAIC this is almost always unexpected and unwanted and just serves to make Hibernate more semantically correct at the expense of productivity and reliability. In ManyToOne situations normally yo...
|