Uploaded image for project: 'MusicBrainz Server'
  1. MusicBrainz Server
  2. MBS-10457

Make A→B merge not fail if B→C merge happened first

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Edit system
    • Labels:
      None

      Description

      @psychoadept wrote on the forums:

      If you merge entity A with entity B, and B is being merged with entity C, but B -> C happens first, then A -> B fails. If the outcome of merging is that the merge target takes on the identity and relationships of the merge subject, I don’t understand why the system can’t handle this. It seems like simple logic, A=B and B=C therefore A=C.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              freso Frederik “Freso” S. Olesen
            • Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:

                Packages

                Version Package