[DDC-952] Several features to batch eager selects more efficently Created: 27/Dec/10  Updated: 11/Sep/13  Resolved: 11/Sep/13

Status: Resolved
Project: Doctrine 2 - ORM
Component/s: ORM
Affects Version/s: None
Fix Version/s: 2.2
Security Level: All

Type: New Feature Priority: Major
Reporter: Benjamin Eberlei Assignee: Benjamin Eberlei
Resolution: Fixed Votes: 1
Labels: None

DDC-733 Implement a way of forcing a Persiste... Sub-task Resolved Benjamin Eberlei  
DDC-734 Possibility to fetch all outstanding ... Sub-task Closed Guilherme Blanco  
DDC-53 Introduce batching of eager loads Sub-task Resolved Benjamin Eberlei  
DDC-914 Use JOIN for Fetch=EAGER ManyToOne an... Sub-task Resolved Benjamin Eberlei  
DDC-1060 Use Hydrators inside Persisters Sub-task Resolved Benjamin Eberlei  
DDC-963 @OneToOne inverse side executes queri... Sub-task Resolved Benjamin Eberlei  
DDC-865 Passing an array as parameter Sub-task Resolved Benjamin Eberlei  


This ticket aggregates several strategies to optimize batching of eager selects.

Comment by Benjamin Eberlei [ 31/Dec/10 ]

Requirements for batching of eager loads:

1. Since we are using an IN() query for this we can only support this feature for entities that have a single column primary key.
2. If we want to support composite keys we need to build it as WHERE ( (id1 = ? AND id2 = ?) OR (id1 = ? AND id2 = ?)) but this is currently not possible with the way how internally the $criteria array is used.

Comment by Benjamin Eberlei [ 31/Dec/10 ]

Next item to think about: What if an exception or event breaks the flow and "triggerEagerLoads()" is never called?

Generated at Mon Aug 31 01:04:11 EDT 2015 using JIRA 6.4.10#64025-sha1:5b8b74079161cd76a20ab66dda52747ee6701bd6.