Doctrine 2 - ORM
  1. Doctrine 2 - ORM
  2. DDC-547

Consider allowing custom PersistentCollection implementations

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • 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

        Hide
        Marco Pivetta added a comment -

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

        Show
        Marco Pivetta added a comment - This can't be solved in the 2.x series because of the tight coupling between association UnitOfWork logic and the PersistentCollection API.
        Hide
        Wouter Wiltenburg added a comment -

        Any progress on this new feature?

        Show
        Wouter Wiltenburg added a comment - Any progress on this new feature?
        Hide
        Benjamin Eberlei added a comment -

        Reschedule for 2.x

        Show
        Benjamin Eberlei added a comment - Reschedule for 2.x
        Hide
        Roman S. Borschel added a comment -

        Rescheduled for 2.1. Might be 2.x.

        Show
        Roman S. Borschel added a comment - Rescheduled for 2.1. Might be 2.x.

          People

          • Assignee:
            Roman S. Borschel
            Reporter:
            Roman S. Borschel
          • Votes:
            7 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

            • Created:
              Updated: