You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#project4, In the Insert executors, when I tried to maintain the write sets in transactions, the Abort() method returned me an error.
Then I found it occur because the TableWriteRecord was already added to write sets by TableHeap::InsertTuple() method, as well as TableHeap::MarkDelete() and TableHeap::UpdateTuple(). So when I called AppendTableWriteRecord(const TableWriteRecord &write_record), the same record will be added twice.
That's not so reasonable for me. I thought maintaining TableWriteRecord and IndexWriteRecord both in write sets, but now only the IndexWriteRecord needs to do. Hope it can be improved.
This discussion was converted from issue #211 on September 16, 2022 04:13.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
#project4, In the Insert executors, when I tried to maintain the write sets in transactions, the Abort() method returned me an error.
Then I found it occur because the TableWriteRecord was already added to write sets by TableHeap::InsertTuple() method, as well as TableHeap::MarkDelete() and TableHeap::UpdateTuple(). So when I called AppendTableWriteRecord(const TableWriteRecord &write_record), the same record will be added twice.
That's not so reasonable for me. I thought maintaining TableWriteRecord and IndexWriteRecord both in write sets, but now only the IndexWriteRecord needs to do. Hope it can be improved.
Beta Was this translation helpful? Give feedback.
All reactions