[DDC-2919] Make lock mode usage consistent #932
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hello, thank you for creating this pull request. I have automatically opened an issue http://www.doctrine-project.org/jira/browse/DDC-2952 We use Jira to track the state of pull requests and the versions they got |
|
👍 |
beberlei
added a commit
that referenced
this pull request
Feb 8, 2014
[DDC-2919] Make lock mode usage consistent
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes ORM's method signatures to declare a default lock mode of
nullinstead ofLockMode::NONEto make lock mode usage consistent and predictable on platforms supportingLockMode::NONEtable lock hints (currently SQL Server and SQL Anywhere).Please see
UPGRADE.mdand DDC-2919 for further details.