You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the Jackrabbit implementation (not tried in DBAL) when you try and save a session after removing a node with references the save fails and a PHPCR\ReferentialIntegrityException is thrown.
However, when catching this error and calling:
$node->getReferrers();
I get the following error:
Path not found (node deleted in current session)
The text was updated successfully, but these errors were encountered:
i think there are many places in jackalope (and also the odm) where the internal state gets messed up after an exception is thrown because of some violation. it had a lower priority to us because usually the request / script will have to bail out after an error anyways. maybe the best after an error would be to aquire a new session...
if we can improve the recoverability after an error without overcomplicating everything, i am +1 of course, it would be nice if you could continue after an exception.
With the Jackrabbit implementation (not tried in DBAL) when you try and save a session after removing a node with references the save fails and a
PHPCR\ReferentialIntegrityException
is thrown.However, when catching this error and calling:
I get the following error:
The text was updated successfully, but these errors were encountered: