Re: Can you prevent commits from a client application?
From: dean <deanbrown3d_at_yahoo.com>
Date: Fri, 15 Aug 2008 17:29:21 -0700 (PDT)
Message-ID: <11d265dc-e4e5-4216-9fff-dc3d6f87b073@26g2000hsk.googlegroups.com>
Date: Fri, 15 Aug 2008 17:29:21 -0700 (PDT)
Message-ID: <11d265dc-e4e5-4216-9fff-dc3d6f87b073@26g2000hsk.googlegroups.com>
On Jul 16, 3:30 pm, Kai Rode <nik..._at_web.de> wrote:
> >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).
>
> My idea (haven't had time to test yet): Create a table with a deferred
> constraint CHECK (1=0). Insert a row into that table, then let your testers
> play. If anyone tries to commit, the commit will be prevented by the failed
> checking of the deferred constraint.
Interesting! I'll try it and post up either way whether it works or not.
Thanks!
-Dean Received on Fri Aug 15 2008 - 19:29:21 CDT