Overview
In daily life, our use of the for update is still relatively common, especially in the manual modification of data in the case of PL/SQL developer.
It is only convenient at this point, and the true meaning of the for update lacks understanding:
The for update is a special case of Oracle's manual increase in lock level and range, and Oracle's lock mechanism is a good one for various types of database lock mechanisms.
Therefore, Oracle believes that there is generally no need for users and applications to directly lock control and promotion, and even the deadlock of such a lock-related problems of the scene, mostly related to manual lifting lock.
Therefore, Oracle does not recommend using the for update as a daily development use. Moreover, in peacetime development and operation, use for update but forget to commit, will cause a lot of lock table failure.
PL/SQL Developer modifying data suggests this form: select T.*,t.rowid from table t;
"Use Scene"
When you need business-level data exclusivity, consider using a for update.
On the scene, such as train tickets booking, the screen shows a ticket, while the actual ticket, you need to re-determine that the data is not modified by other clients. So, in this confirmation process, you can use the for update.
About Oracle for update