Understanding Oracle Row-level locks

When you update the same row of records concurrently, the post-update connection needs to wait for the first update to commit or roll back. 3 Graphs to help understand:

1 , New command window, update id=1 line, there is echo can continue to execute other SQL, connection is in a commit or rollback state;

2 , and then open the Command window, still update id=1 line, no echo, the connection is waiting, waiting for the lock to get the row;

3 , after switching to the 1th window for submission, the connection of the 2nd window is in a committed state;

Understanding Oracle Row-level locks