Details
Sub-task
Open
Minor
Description
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.
Activity
Roman S. Borschel
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Parent |
|
|
| Issue Type | New Feature [ 2 ] | Sub-task [ 5 ] |
Benjamin Eberlei
made changes -
| Fix Version/s | 2.x [ 10090 ] | |
| Fix Version/s | 2.1 [ 10022 ] |
Benjamin Eberlei
made changes -
| Workflow | jira [ 11628 ] | jira-feedback [ 13864 ] |
Benjamin Eberlei
made changes -
| Workflow | jira-feedback [ 13864 ] | jira-feedback2 [ 15728 ] |
Benjamin Eberlei
made changes -
| Workflow | jira-feedback2 [ 15728 ] | jira-feedback3 [ 17985 ] |
This list may be incomplete, as errors occurred whilst retrieving source from linked applications:
- Request to http://www.doctrine-project.org/fisheye/ failed: Error in remote call to 'FishEye 0 (http://www.doctrine-project.org/fisheye/)' (http://www.doctrine-project.org/fisheye) [AbstractRestCommand{path='/rest-service-fe/search-v1/crossRepositoryQuery', params={query=DDC-691, expand=changesets[-21:-1].revisions[0:29],reviews}, methodType=GET}] : Received status code 503 (Service Temporarily Unavailable)
Any news?
Why query hint? What about temporary switching like fetch mode changing via query object?