Re: Can you prevent commits from a client application?

From: Ana C. Dent <anacedent_at_hotmail.com>
Date: Wed, 09 Jul 2008 00:54:43 GMT
Message-ID: <Xns9AD5B5D337552anacedenthotmailcom@69.28.173.184>


dean <deanbrown3d_at_yahoo.com> wrote in news:18ccb7fd-35ad-47a5-ac0d- 8eedf96faa57_at_b1g2000hsg.googlegroups.com:

> 10g. Is there any way to alter a session and prevent ANY commits (at
> least until a subsequent call to remove the alteration)? I'm using the
> following statement to prevent commits in any procedures (ALTER
> SESSION DISABLE COMMIT IN PROCEDURE), but I need a way to prevent
> accidental commits from within a client application.
>
> The reason I would like this is to allow testers to be able to
> navigate around an application after a databridge has been run, and
> poke around here and there in various datagrids, without risk of them
> accidentally calling a function that has a commit in it.
>
> Any thoughts appreciated.
>

Provide a READ ONLY schema Received on Tue Jul 08 2008 - 19:54:43 CDT

Original text of this message