Bug #5600
nested domain-models produce a endless loop
Status: | Closed | Start date: | 2009-12-02 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | - | % Done: | 0% |
|
Category: | - | |||
Target version: | - |
Description
Hi,
I have special nested domain-models. To reproduce the Bugs it is necessary to use no Lazy SplStorageObjects. I have two classes. Each class has a property to store the other class in a SplStorageObject.
The class backend.php calls the method persistObject($object). The Objects in the SplStorageObject are stored in a QUEUE. All objects in the QUEUE are persisted again (persistObject($object)). It is a endless loop to persist the nested object.
Error: Fatal Error: Maximum function nesting level of …
One solution would be to persist only objects that have not been saved so far.
The second problem occurs with an update. The method replaceObject() removes the oldObject1 from the identity-mapper.
persistObject():
updatedObject1 -> SPL -> Object2 (AOPProxy) -> SPL -> OldObject1 = cant find the UID and the OldObject1 in the Idenity-Mapper
Error: CRITICAL TYPO3 Uncaught Exception 1246892970
History
#1 Updated by Karsten Dambekalns over 4 years ago
- Status changed from New to Closed