3 ms·
While time is down, it's the time of a hypothetical user entering the command, not the time at which commands actually affect data in the table. I think that's
by kornish 10y ago
While time is down, it's the time of a hypothetical user entering the command, not the time at which commands actually affect data in the table. I think that's pretty intuitively clear to the reader, especially since the article is about counterintuitive behavior.
- quizotic 10y agoThe point is that if a user on the right entered the update command, it would NOT return until after the transaction on the left committed, because there's a database lock on the balance when the left transaction did its update.