Before updating the table with update on a test machine, there is no commit, and there is no PL/SQL Developer.
The next day, view the table on your own computer and find that the record is not updated
I want to update it with the SQL statement, the execution of more than 10 minutes has not finished.
To re-update manually, prompt:
At this point, the table has been found to be locked, because the previous use of the test machine update but did not commit (COMMIT)!!
DML operations such as Insert,delete,Update,select...for update, and so on, will touch the post-level and row-level locks,
After the DML operation, the table is locked before the commit operation, and other transactions cannot manipulate the table!
Therefore, after the DML operation, remember to add a statement: commit; or click Commit manually.
In addition, PL/SQL developer provides auto-commit settings:
A. Auto-commit after transaction execution: Preferences Windows Types, Tools---SQL window: tick "autocommit SQL" to automate the commit operation.
B. Exit Login Auto-commit: Log off with open transaction, Connection, Tools--Preferences--select "Commit".
PL/SQL Developer settings for autocommit transactions