Remove versioned offset ranges from transactions and undo operations
Now, instead of using these versioned offset ranges, we locate the fragments associated with a transaction using the transaction's edit ids. To make this possible, buffers now store a new map called `insertion_slices`, which lets you look up the ranges of insertions that were affected by a given edit. Co-authored-by: Antonio Scandurra <antonio@zed.dev>
This commit is contained in:
parent
65fd943509
commit
7c3421e041
3 changed files with 137 additions and 178 deletions
|
@ -535,7 +535,6 @@ message Transaction {
|
|||
repeated LocalTimestamp edit_ids = 2;
|
||||
repeated VectorClockEntry start = 3;
|
||||
repeated VectorClockEntry end = 4;
|
||||
repeated Range ranges = 5;
|
||||
}
|
||||
|
||||
message LocalTimestamp {
|
||||
|
@ -890,7 +889,6 @@ message Operation {
|
|||
uint32 local_timestamp = 2;
|
||||
uint32 lamport_timestamp = 3;
|
||||
repeated VectorClockEntry version = 4;
|
||||
repeated Range transaction_ranges = 5;
|
||||
repeated VectorClockEntry transaction_version = 6;
|
||||
repeated UndoCount counts = 7;
|
||||
}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue