Website (required)

VocaDB

Describe the bug (required)

Voice synth "associated artists" field loses data(?) in a specific situation related to artist merges (the merged entry and the merge target entry both are "associated artists")?

After an entry merge relating to the voice provider, the voice provider field was not updated:

• https://vocadb.net/Ar/143905 (U) had https://vocadb.net/Ar/143904 (A) as "voice provider" and https://vocadb.net/Ar/56981 (B) as "manager" (https://vocadb.net/Artist/Versions/143905 revision 5 https://vocadb.net/Artist/ArchivedVersionXml/481111);
• https://vocadb.net/Ar/143904 (A) was merged into https://vocadb.net/Ar/56981 (B);
• https://vocadb.net/Ar/143904 (A) still listed https://vocadb.net/Ar/143905 (U) under "Voice provider of";
• however, https://vocadb.net/Ar/143905 (U) simultaneously did not list any voice provider after the merge of A into B, and B had to be added manually
  • (https://vocadb.net/Artist/Versions/143905 revision 6: null edit to see if A would be un-associated or B would appear; revision 7: adding B);
• and https://vocadb.net/Ar/143904 (A) still lists https://vocadb.net/Ar/143905 (U) under "Voice provider of", after all of this
  • (the association is still in the database but not shown because A is deleted?).
  • This seems to be different from other merging-related behavior (for example, "All songs" is now empty)
  • This seems to be specifically because both A and B were "associated artists" for U
    • I tried testing on the beta website but got confused tbh. but see https://beta.vocadb.net/Ar/143976 ("Voice provider of: test UTAU") and https://beta.vocadb.net/Ar/143974 (no voice provider listed)

To Reproduce (optional)

see above

Expected behavior (optional)

see above

Screenshots (optional)

Desktop (optional)

• N/A

Smartphone (optional)

• N/A

Additional context (optional)

Checklist (required)

Fill out the checklist. Use strikethroughs or leave fields empty if you don't know or are unable to check/test.

• Searched VocaDB/vocadb for duplicate issues.
• Tested on the beta site.
• Tested on different browsers (e.g. Firefox, Chrome, Safari, Edge).
• Checked in private mode.
• Cleared browser cache and cookies.
• Checked the DevTools console.
• Checked the syslog (mods+ only).