Re: Can you prevent commits from a client application?

On Jul 9, 8:58 pm, Steve Howard <stevedhow..._at_gmail.com> wrote:
> On Jul 9, 7:37 pm, dean <deanbrow..._at_yahoo.com> wrote:
>
>
>
>
>
> > On Jul 8, 8:54 pm, "Ana C. Dent" <anaced..._at_hotmail.com> wrote:
>
> > > dean <deanbrow..._at_yahoo.com> wrote in news:18ccb7fd-35ad-47a5-ac0d-
> > > 8eedf96fa..._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
>
> > Can you set read-only from a client program, at run time?
>
> Look up secure application roles, if you want to specify what a
> certain application user can do under specific conditions.- Hide quoted text -
>
> - Show quoted text -

Sorry I'm not being clear here - I would like do a series of updates and inserts, and then once all that is finished, turn off any ability to make changes. In other words, a run-time and dynamic change in the read-only state (such as with alter session). Received on Wed Jul 09 2008 - 21:49:47 CDT