[DDC-547] Consider allowing custom PersistentCollection implementations Created: 27/Apr/10  Updated: 20/May/14

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

Type: New Feature Priority: Minor
Reporter: Roman S. Borschel Assignee: Roman S. Borschel
Resolution: Unresolved Votes: 7
Labels: None


 Description   

We should consider allowing the configuration of custom PersistentCollection implementations on a per-association basis.
This could allow users to craft optimized (SQL) behavior for for some of their collections to improve performance without changing the domain model code.

For this, PersistentCollection needs to be designed for inheritance.



 Comments   
Comment by Roman S. Borschel [ 26/Aug/10 ]

Rescheduled for 2.1. Might be 2.x.

Comment by Benjamin Eberlei [ 24/Dec/10 ]

Reschedule for 2.x

Comment by Wouter Wiltenburg [ 20/May/14 ]

Any progress on this new feature?

Comment by Marco Pivetta [ 20/May/14 ]

This can't be solved in the 2.x series because of the tight coupling between association UnitOfWork logic and the PersistentCollection API.

Generated at Thu Oct 30 18:58:26 UTC 2014 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.