You need it for the post commit insert event.
But we could optimize that if there is no such event.
On Nov 9, 2007, at 21:21, Markus Heiden wrote:
After executing actions, the actions (e.g. EntityInsertAction) will
be moved from ActionQueue.inserts etc. to ActionQueue.executions to
stay the
Hi Darryl,
the problem is the memory consumption. The database has no problems with the
size of the transaction (I tested this by increasing the max heap size to 1
GB). The workaround I use works for now, so that I need no complex solution
for first. My intend was to find a real solution for t
Markus Heiden wrote:
After executing actions, the actions (e.g. EntityInsertAction) will be
moved from ActionQueue.inserts etc. to ActionQueue.executions to stay
there until the transaction completes. Because they do have a reference
to the instance being saved, they prevent that instance from
After executing actions, the actions (e.g. EntityInsertAction) will be moved
from ActionQueue.inserts etc. to ActionQueue.executions to stay there until
the transaction completes. Because they do have a reference to the instance
being saved, they prevent that instance from being garbage collect
