Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hotfix - #1169 - extra lazy one to many must be no-op when not doing orphan removal #1288

Conversation

Ocramius
Copy link
Member

See #1281 (comment)

Linking #1169

…nges should be no-op unless orphan removal is specified.
…nges should be no-op unless orphan removal is specified.
…on should not be updated directly if no orphan removal is involved
…n-removal, referenced entities should be deleted directly
@doctrinebot
Copy link

Hello,

thank you for creating this pull request. I have automatically opened an issue
on our Jira Bug Tracker for you. See the issue link:

http://www.doctrine-project.org/jira/browse/DDC-3544

We use Jira to track the state of pull requests and the versions they got
included in.

…ed cache entries should be evicted to avoid collisions with DB state
@@ -485,7 +486,7 @@ public function testRemoveElementOneToMany()

$this->assertFalse($user->articles->isInitialized(), "Post-Condition: Collection is not initialized.");
// NOTE: +2 queries because CmsArticle is a versioned entity, and that needs to be handled accordingly
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comment can be removed, right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep

@Ocramius Ocramius self-assigned this Jan 28, 2015
Ocramius added a commit that referenced this pull request Jan 28, 2015
…-many-is-noop-when-not-doing-orphan-removal

Hotfix - #1169 - extra lazy one to many must be no-op when not doing orphan removal
@Ocramius Ocramius merged commit 3ed73b4 into doctrine:master Jan 28, 2015
@Ocramius Ocramius deleted the hotfix/#1169-extra-lazy-one-to-many-is-noop-when-not-doing-orphan-removal branch January 28, 2015 20:27
@lcobucci lcobucci added this to the 2.5 milestone Dec 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants