The undeleted row would have invalid `row-id` and `last-updated-seq-num`. Since it is a new row (added back), it should have the `row-id` higher than or equal to the snapshot's `first-row-id` and the `last-updated-seq-number` should inherit/have the new snapshot's sequence number.
On Fri, Nov 21, 2025 at 11:48 AM Steven Wu <[email protected]> wrote: > Hi, > > Should we clarify the V3 spec to explicitly formid "*undelete*" of a row > by unsetting the DV bit? Unsetting a DV bit essentially adds a row with > lower row-id than the snapshot's first-row-id, which would violate the row > lineage spec. With the restriction, DV cardinality should be monotonically > increasing. > > Thanks, > Steven >
