out to lunch

> Subject: Re: ANSI vs. Non-ANSI > Date: 6 Jan 1995 00:02:39 GMT > Reply-To: junet@informix.com (June Tong) > Organization: Informix Software, Inc. > > In article <dberg.789147595@cheetah> dberg@informix.com (David I. Berg) writes: > >Third, the isolation level for applications running against ANSI databases > >defaults to Repeatable Read. This can wreak havoc with concurrency > >control and lock management. (With Repeatable Read every row selected > >within a cursor has a shared lock placed on it from the time the first such > >row is fetched until the cursor is closed.) > > Of course, you can always change the isolation level within your application, > but just wait until the first time someone runs: > SELECT * FROM sometable;> and then goes to lunmch. > > June Yes, the out-to-lunch bunch can cause havoc in a production environment. I have a 4gl-callable timer routine that can protect you from idle applications that do not log out of the database, but not from someone doing the above from ISQL or DBaccess. This Informix 4GL callable C code is available to anyone who wants it. It's free, so no warranties; but it has been tested under BSD and SysV versions of Unix, even on Sinix. Write if you are interested. Regards, Alan ___________________________ ______________________| R. Alan Popiel |__________________________ \\ Internet: | Martin Marietta, SLS | / \\ alan@den.mmc.com | P.O. Box 179, M/S 3810 | Std disclaimers apply. / )Voice: | Denver, CO 80201-0179 USA | ( / 303-977-9998 |___________________________| (But you knew that!) \\ /________________________) (____________________________\\