Doctrine 2 - ORM
  1. Doctrine 2 - ORM
  2. DDC-2168

[GH-523] [DDC-2074] Bugfix regarding clearing cloned PersistentCollections

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.3.1
    • Component/s: None
    • Security Level: All
    • Labels:
      None

      Description

      This issue is created automatically through a Github pull request on behalf of jankramer:

      Url: https://github.com/doctrine/doctrine2/pull/523

      Message:

      When calling clear on a PC that has no owner (e.g. because it was cloned), it can't be deleted as there is no metadata available (that's essentially the exception mentioned in the ticket). In these cases, I think it shouldn't be scheduled for deletion, but please have a look as my knowledge of the ORM internals is limited.

        Activity

        Hide
        Benjamin Eberlei added a comment -

        A related Github Pull-Request [GH-523] was closed
        https://github.com/doctrine/doctrine2/pull/523

        Show
        Benjamin Eberlei added a comment - A related Github Pull-Request [GH-523] was closed https://github.com/doctrine/doctrine2/pull/523
        Hide
        Doctrine Bot added a comment -

        A related Github Pull-Request [GH-523] was closed:
        https://github.com/doctrine/dbal/pull/523

        Show
        Doctrine Bot added a comment - A related Github Pull-Request [GH-523] was closed: https://github.com/doctrine/dbal/pull/523

          People

          • Assignee:
            Benjamin Eberlei
            Reporter:
            Benjamin Eberlei
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: