The constraint that only one item can have a given combination of label and description per language is nice to have, but hard to enforce: the consistency requirements need transactional logic, which causes excessive lock retention and time outs. So, just drop it.
Note that we still need to keep the "unique label per language" constraint on properties (and probably also on queries). Maybe we need a dedicated DB table for these.
Version: unspecified
Severity: normal
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T30599 Deadlock tracking bug (tracking) | |||
| Resolved | daniel | T44547 TermSqlCache deadlocks | |||
| Resolved | None | T44754 editing of item having same label/description as another item at a different language is not possible | |||
| Declined | None | T44685 Remove the label/description uniqueness constraint for items |
The requirement here is not to remove the check for conflicting items upon save: we can keep that check, as and advisory. But we can't *guarantee* uniqueness of label/description/language efficiently, and we shouldn't try. So, updates of the wb_term table should be reviewed to minimize lock retention.