Actions
Feature proposal #9011
closedRewrite cbrepeat re-ordering behavior
Description
This currently causes re-indexing of the row being changed and all subsequent rows, but is this really necessary? It should insert a new row then never touch the row id again. The current re-ordering behavior can result in data loss if the re-indexing fails for any reason. This gets especially complicated when dealing with repeat usages within repeat usages.
Updated by krileon about 2 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Implemented in MR !1817
Actions