-
|
I am currently studying the DragonflyDB codebase and have learned a lot from it. However, I have encountered some confusion regarding the transaction logic, particularly with the LMOVE command. From what I understand, the LMOVE command does not seem to guarantee transaction isolation. It appears to operate in two distinct phases: the first phase executes a PEEK operation, and the second phase executes PUSH and POP operations. If other commands modify the list between these two phases, could this potentially lead to data inconsistency? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
As you can see in your editor, we execute the first hop with |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your reply. ❤️ |
Beta Was this translation helpful? Give feedback.
As you can see in your editor, we execute the first hop with
conclude:false. That means is that these keys stay logically "locked" for modifications until the transaction concludes. The second hop unlocks these keys.