Re: Can you prevent commits from a client application?

From: Steve Howard <stevedhoward_at_gmail.com>
Date: Wed, 9 Jul 2008 17:58:38 -0700 (PDT)
Message-ID: <03fe86d3-4bd3-400d-ba1d-1e69e69c2c6d@x41g2000hsb.googlegroups.com>


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. Received on Wed Jul 09 2008 - 19:58:38 CDT

Original text of this message