Hi Markus I stopped upgrading from 1.4.2 so you may want to check the release notes while reading my answer.
I remember having similar issues with cascades in my JPA annotated classes. Try and `detach` your Set<B> attribute by calling the getter on the proxy instance returned by OrientDB, and then remove it from the database. The behavior you're describing is the intended purpose of `orphanRemoval`. We gave up using the object database abstraction to go back to the document one precisely because, in our opinion, OrientDB is not JPA consistent, let alone compliant. And this was causing tremendous headaches. But again, please refer to the release notes as some of the fixes could have addresses those very issues. Best -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
