[DC-436]  Change in 1.2 to Doctrine_Event::skipOperation() functionality Created: 18/Jan/10  Updated: 10/Feb/10

Status: Open
Project: Doctrine 1
Component/s: Relations
Affects Version/s: 1.2.1
Fix Version/s: 1.1.6

Type: Bug Priority: Major
Reporter: Cameron Ross Assignee: Jonathan H. Wage
Resolution: Unresolved Votes: 0
Labels: None
Environment:

Debian



 Description   

I have been using Doctrine 1.1.6.

I have two related models, which are always saved together. In my application, save is called on class A and that save cascades to class B. I have a save listener which in some cases can intercept class A's save operation and call Doctrine_Event::skipOperation() to prevent class A from being persistently saved. However, in such cases, class B is still saved - the skipOperation() does not skip the entire operation, just class A's save operation, allowing subsequent operations to occur as normal.

This is the desired functionality and has been working fine. However, I have just upgraded to 1.2.1. only to find that something has changed, causing the skipOperation() to skip the entire operation, therefore not saving class B when class A's listener interferes.

I presume this is a bug. If not, what precisely has changed with skipOperation(), and how can I keep the traditional functionality?






Generated at Tue Sep 30 21:57:30 UTC 2014 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.