Re: Can you prevent commits from a client application?

From: dean <deanbrown3d_at_yahoo.com>
Date: Wed, 9 Jul 2008 16:37:51 -0700 (PDT)
Message-ID: <35e633f9-ed24-4f8a-a5aa-f6cd05fb0153@l42g2000hsc.googlegroups.com>

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? Received on Wed Jul 09 2008 - 18:37:51 CDT

Original text of this message