Oracle commit usage

The first bug fix uses the Oracle update statement.

Update Table1 set web =-1 where progid = n'000000'

Codereview

Do we need a commit; in the Oracle version?

I checked Oracle commit usage online

Commit

Purpose

UseCOMMITStatement to end your current transaction and make permanent all changes stored med in the transaction. A transaction is a sequence of SQL statements that Oracle Database treats as a single unit. this statement also erases all savepoints in the transaction and releases transaction locks.

Until you commit a transaction:

• You can see any changes you have made during the transaction by querying the modified tables, but other users cannot see the changes. after you commit the transaction, the changes are visible to other users 'statements that execute after the commit.

• You can roll back (UNDO) any changes made during the transaction withROLLBACKStatement (see rollback.

Oracle Database issues an implicitCOMMITBefore and after any Data Definition Language (DDL) statement.

You can also use this statement

• Commit an in-doubt Distributed Transaction manually

• Terminate a read-only transaction begun bySET TRANSACTIONStatement

Oracle recommends that you explicitly end every transaction in your application programs withCOMMITOrROLLBACKStatement, including the last transaction, before disconnecting from Oracle database. If you do not explicitly commit the transaction and the program terminates abnormally, then the last uncommitted transaction is automatically rolled back.

A normal exit from most Oracle utilities and tools causes the current transaction to be committed. A normal exit from an oracle precompiler program does not commit the transaction and relies on Oracle database to roll back the current transaction.