#111294eval=unique treats workspace versions of a live record as duplicates
Description
For a workspace-aware table, a field with eval=unique is wrongly renamed (e.g. foo becomes foo0) when the record is saved while a version of it exists in a workspace.
- Use a
versioningWStable with aeval=uniquecolumn. - Create a live record, then create a version of it in workspace 1, while both records have the same value.
- Save the live record in the live workspace without changing the value.
Result: the value is changed to foo0, with the log message “has been changed … as it is required to be unique”.
Expected: the value stays unchanged.
The same happens when a version is saved in workspace 1 while another workspace also has a version of the same live record.
Reviews 1
History 01
-
Gerrit Code Review pushed patch set 1 for main to change 97242 status
NewUnder Review <span data-processor="relativetime" data-value="2026-10-30T17:16:19+00:00" > 10/30/26, 17:16 </span>