Orm: DDC-547: Consider allowing custom PersistentCollection implementations

[doctrinebot]

Jira issue originally created by user romanb:

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.

[doctrinebot]

Comment created by romanb:

Rescheduled for 2.1. Might be 2.x.

[doctrinebot]

Comment created by @beberlei:

Reschedule for 2.x

[doctrinebot]

Comment created by Wilt:

Any progress on this new feature?

[doctrinebot]

Comment created by @ocramius:

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

[Arkemlar]

@ocramius can you give recommendation about how to make workaround of this limitation? Custom collections is really needed in domain logic.

[Ocramius]

There is no possible workaround right now.

On 5 Mar 2017 3:57 p.m., "Yanosh" [e-mail] wrote:

@ocramius https://github.com/ocramius can you give recommendation about
how to make workaround of this limitation? Custom collections is really
needed in domain logic.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/doctrine/doctrine2/issues/5057#issuecomment-284233242,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJakJyx3QXHo3V8P9x-iKE7sRWFnWUGks5ris1MgaJpZM4MTb52
.

[Itach1Uchixa]

Little workaround @Arkemlar : https://gist.github.com/Itach1Uchixa/83fedd850e4705b0b51589afaefdfdf1

[hugochinchilla]

Any progress on this?

[Ocramius]

@hugochinchilla no, this is likely not going to be solved for 3.x either due to its complexity

[Ocramius]

Gonna close here as "won't fix".

While the feature is a "most wanted", having a placeholder isn't useful until someone comes up with an implementation plan that is viable and that can be attempted.

Please open a new issue if you have an approach that you think could work (considering lazy-loading and UnitOfWork semantics).