-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
DDC-691: doctrine.readOnly query hint #5202
Milestone
Comments
Comment created by koc: Any news? |
Comment created by acid24: Any news on this? I think this is a must have feature. Thanks for all your work. |
beberlei
added a commit
that referenced
this issue
Mar 1, 2021
beberlei
added a commit
that referenced
this issue
Mar 1, 2021
beberlei
added a commit
that referenced
this issue
Apr 18, 2021
Merged into 2.9.x |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jira issue originally created by user romanb:
Setting such a query hint to TRUE should result in all entities being retrieved by that query to be read-only for the purposes of change-tracking. Note that the entities themselves need not necessarily be read-only in general.
This feature is a flush performance tweak that can be used to query for objects but not let the returned objects run through change-tracking on flush. Any other managed objects are tracked as usual so you can do a read-only query for 100 entities and persist a new entity in the same unit of work with optimal flushing performance.
The text was updated successfully, but these errors were encountered: