review(wave-a L1): correct concurrency-catch comment (no DB uniqueness on effective name)
Claude-Session: https://claude.ai/code/session_01LVneM3eh1UtJxEisFXgmox
This commit is contained in:
@@ -248,7 +248,9 @@ public sealed class UnsTreeService(
|
|||||||
}
|
}
|
||||||
catch (DbUpdateException)
|
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.");
|
return new UnsMutationResult(false, "Add failed — a reference at one of these tags was created concurrently. Reload and retry.");
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user