Re: <No Subject Supplied>

In article <1993Jul8.143903.18109@informix.com>, davek@newjersey.informix.com (Dave Kosenko) writes: > > naomi@qip.anasazi.com writes: > |> > Alternatively, if you don't actually need Committed Read isolation, just > |> > SET ISOLATION TO DIRTY READ, and it will work fine. > |> > |> The problem I have with setting ISOLATION is that it affects the entire > |> database, and sometimes I only want a particular table. > > You could, of course, only execute the isolation change immediately before > querying that table, then set it back as soon as you are done. ^^^^^^^^^^^ That's correct, as far as it goes. We've encountered, a problem, however, in that we sometimes want to write modular library routines. Thus, we DON'T KNOW what the original level was to set it back to. And there's no way of querying the engine that we know of. [I guess this is really an enhancement request]. As always, just my opinion - I don't speak for AT&T, etc. Ihor Kinal att!trumpet!ijk