Re: How to trap a commit from an application?

"dean" <deanbrown3d_at_yahoo.com> wrote in news: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 on-
> commit 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.
>
>

IMO, not possible & NOT desirable.
What you descripe is RIPE for many ugly deadlocks. Received on Thu Feb 01 2007 - 10:05:59 CST