Hotfix - #1169 - extra lazy one to many must be no-op when not doing orphan removal#1288
Merged
Ocramius merged 10 commits intodoctrine:masterfrom Ocramius:hotfix/#1169-extra-lazy-one-to-many-is-noop-when-not-doing-orphan-removalJan 28, 2015
+206-38
Commits
Commits on Jan 27, 2015
doctrine#1169 DDC-3343 - updating test expectations - one-to-many changes should be no-op unless orphan removal is specified.
committeddoctrine#1169 DDC-3343 - updating test expectations - one-to-many changes should be no-op unless orphan removal is specified.
committeddoctrine#1169 DDC-3343 - correcting one-to-many persister - association should not be updated directly if no orphan removal is involved
committeddoctrine#1169 DDC-3343 - adding tests for orphan-removal + extra-lazy + one-to-many element removal behavior
committed- committed
doctrine#1169 DDC-3343 - when using one-to-many extra-lazy with orphan-removal, referenced entities should be deleted directly
committeddoctrine#1169 DDC-3343 - when a deletion fails for some reason, related cache entries should be evicted to avoid collisions with DB state
committeddoctrine#1169 DDC-3343 - eagerly evicting cache if a persister passes a delete operation down to the DB
committeddoctrine#1169 DDC-3343 - eagerly evicting cache if a persister passes a delete operation down to the DB
committed
