Doctrine 2 - ORM
  1. Doctrine 2 - ORM
  2. DDC-678

OneToMany/OneToOne + onDelete=CASCADE may corrupt UoW.

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Security Level: All
    • Labels:
      None

      Description

      OneToMany/OneToOne associations together with an onDelete=CASCADE schema generation hint on the @JoinColumn and appropriate foreign key constraints can potentially result in a corrupt UoW if the associated objects are already managed. We need to add tests for such scenarios and settle on a well-defined behavior in such cases.

        Activity

        Hide
        Benjamin Eberlei added a comment -

        Changed to improvement

        Show
        Benjamin Eberlei added a comment - Changed to improvement
        Hide
        Benjamin Eberlei added a comment -

        Not entirely would it hurt performance, you could check if on-delete => cascade is set. If this is the case you wouldnt need to do an explicit remove using the UnitOfWorks cascade.

        Show
        Benjamin Eberlei added a comment - Not entirely would it hurt performance, you could check if on-delete => cascade is set. If this is the case you wouldnt need to do an explicit remove using the UnitOfWorks cascade.
        Hide
        Benjamin Eberlei added a comment -

        I think to preserve the semantics the following has to happen:

        "on-delete" => "cascade" has to implicitly set cascade = remove. This hurts performance of course vs just using the on-delete, however it won't corrupt the UoW.

        Show
        Benjamin Eberlei added a comment - I think to preserve the semantics the following has to happen: "on-delete" => "cascade" has to implicitly set cascade = remove. This hurts performance of course vs just using the on-delete, however it won't corrupt the UoW.

          People

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

            Dates

            • Created:
              Updated: