Consider allowing custom PersistentCollection implementations

Details

Type: New Feature
Status: Open
Priority: Minor
Resolution: Unresolved
Affects Version/s: 2.0-BETA1
Fix Version/s: 2.x
Component/s: ORM
Security Level: All
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.

Activity

Ascending order - Click to sort in descending order

Roman S. Borschel made changes - 27/Apr/10 11:39 AM

Field	Original Value	New Value
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.	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.