Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.0-BETA3
-
Fix Version/s: None
-
Component/s: None
-
Security Level: All
-
Labels:None
Description
Per default Doctrine 2 adds an IN(...)-part to the query when hydrating an entity where a discriminator column is defined. While this makes sense as a default behavior, it would be pretty helpful if one could disable the WHERE-clause for discriminator columns alltogether for performance optimization.
Activity
Benjamin Eberlei
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Workflow | jira [ 11830 ] | jira-feedback [ 13872 ] |
Benjamin Eberlei
made changes -
| Workflow | jira-feedback [ 13872 ] | jira-feedback2 [ 15736 ] |
Benjamin Eberlei
made changes -
| Workflow | jira-feedback2 [ 15736 ] | jira-feedback3 [ 17993 ] |
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-769, expand=changesets[-21:-1].revisions[0:29],reviews}, methodType=GET}] : Received status code 503 (Service Temporarily Unavailable)
That would obviously produce wrong results. Maybe you can elaborate more with an example.