From ac12eec92473d7a98bbcc7fd2b04e084723fbaa0 Mon Sep 17 00:00:00 2001 From: Joseph Doherty Date: Thu, 16 Jul 2026 06:24:05 -0400 Subject: [PATCH] review(wave-a L1): correct concurrency-catch comment (no DB uniqueness on effective name) Claude-Session: https://claude.ai/code/session_01LVneM3eh1UtJxEisFXgmox --- src/Server/ZB.MOM.WW.OtOpcUa.AdminUI/Uns/UnsTreeService.cs | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/Server/ZB.MOM.WW.OtOpcUa.AdminUI/Uns/UnsTreeService.cs b/src/Server/ZB.MOM.WW.OtOpcUa.AdminUI/Uns/UnsTreeService.cs index a5837358..692df0ad 100644 --- a/src/Server/ZB.MOM.WW.OtOpcUa.AdminUI/Uns/UnsTreeService.cs +++ b/src/Server/ZB.MOM.WW.OtOpcUa.AdminUI/Uns/UnsTreeService.cs @@ -248,7 +248,9 @@ public sealed class UnsTreeService( } catch (DbUpdateException) { - // A concurrent add slipped a same-(equipment,tag) or same-name row past the pre-check. + // The UX_UnsTagReference_Equip_Tag unique index tripped: a concurrent add slipped a + // same-(equipment,tag) row past the pre-check. (Effective-name collisions have no DB + // uniqueness — those are caught by the authoring guard and the deploy gate, not here.) return new UnsMutationResult(false, "Add failed — a reference at one of these tags was created concurrently. Reload and retry."); } }