|Problem with circular references [message #1855325]
||Sat, 08 October 2022 04:07
| Alexander Roytman
Registered: March 2018
I have issue with circular references where creating mutually referencing instances would first insert shallow record with all FK columns null and then update them to proper values. The problem is that many of my FKs are not null not to mention an extra useless update statement. My PK values are not managed by eclipeselink but set explicitly so there is no need to do it that way (flush to get PK values from sequences or identity columns) my referential integrity constraints are all deferred so I do not care much for SQL ordering.
Is there any way to tell eclipselink not to do two step persisting (insert shallow and then update FKs)?
There is a similar issue with delete. Before deleting an instance it tries to set ALL FKs in that instance table to NULL and then delete. It fails on not null columns
I would greatly appreciate if you could point me in right direction
Powered by FUDForum
. Page generated in 0.02412 seconds