You're right! This makes no sense :-( so it was good that there is/was a
bug. I refactored my coding!
Andrus Adamchik schrieb am Fr., 15. Nov. 2024, 20:11:
> With the approach that I suggested, the two copies of the same NEW object
> will be disconnected from each other and live their lives inde
With the approach that I suggested, the two copies of the same NEW object will
be disconnected from each other and live their lives independently. So when one
of the contexts is committed and then another, you'll end up with 2 new rows in
the database. That will solve the immediate problem of fa
