Interesting...someone clever than I can probably construct a Zen view of the
situation.
Absent that, however, COMMIT and ROLLBACK affect the permanence of changes
caused by SQL statements. 0 rows deleted means nothing changed, so you
could as well commit as roll back and the results should be id
Hi Fred,
Even though the delete affected no rows, it does begin a transaction. That
transaction takes up a slot in the SGA transaction table (X$KTCXB) but does not
yet use a slot in one of the rollback segment header block transaction tables.
V$TRANSACTION will not show you this transaction becau
The default Oracle DB behavior is for a transaction to
be committed when the session exits.
This may be overridden in an application ( such as SQLPLUS )
so that the default behavior is a rollback.
I would explicitly commit or rollback were I writing an app.
Jared
On Wed, 14 Feb 2001, Frederik
On Wed, 14 Feb 2001 12:40:25 -0800, Steve Adams wrote:
>If you are not concerned about the retention of a slot in the SGA transaction
>table, then the only impact of not terminating the transaction explicitly with a
>COMMIT or ROLLBACK is that the snapshot SCN for consistent reads for subsequent
