Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> How to trap a commit from an application?

How to trap a commit from an application?

From: dean <deanbrown3d_at_yahoo.com>
Date: 31 Jan 2007 20:20:44 -0800
Message-ID: <1170303644.109887.72820@s48g2000cws.googlegroups.com>


Is there any way I can say to Oracle (9.2 or 10g) that if an application attempts to call commit, then throw an exception? An oncommit  event?

The business logic is thus: (1) Begin transaction; (2) Perform large refresh operation from alternate data source (access, via staging tables in a different schema); (3) Allow user to navigate around the application to verify that the data looks sound, and: (4) Then (and ONLY then) call a commit if desired.

The problem I have is that there are ddl-procedure calls, truncates, etc. and other third-party hard-to-capture sources of commit (grids, for example) that are implemented in the application, and which may be called accidentally during step 3. I'd rather put a hold on all commits at the oracle level, if that's possible.

Thanks for any recommendations.
-Dean

Oracle 9.2i, 10g, Windows, ADO. Received on Wed Jan 31 2007 - 22:20:44 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US