home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!ames!olivea!gossip.pyramid.com!pyramid!infmx!aland
- From: aland@informix.com (Colonel Panic)
- Newsgroups: comp.databases.informix
- Subject: Re: defer interrupt.
- Message-ID: <1992Nov8.025246.23843@informix.com>
- Date: 8 Nov 92 02:52:46 GMT
- References: <5576@krafla.rhi.hi.is>
- Sender: news@informix.com (Usenet News)
- Organization: Helen Keller Bondurant's Performance Driving School for the Blind
- Lines: 28
-
- In article <5576@krafla.rhi.hi.is> gaukur@rhi.hi.is (Kristjan Gaukur Kristjansson) writes:
- >I'm currently trying to figure out how to properly use 'defer interrupt'
- >and 'options sql interrupt on' to stop sql queries.
- >
- >I know I have to check on int_flag everywhere but when I try to use it
- >with 'foreach' loops then I don't seem to have much control over when
- >it's detected.
- >
- >Are there any guidelines out there on the best use of this feature or
- >something that helps me better to understand this.
- >(F.ex. should I rather use open,fetch,close than foreach. Shall I use it
- >after every possible SQL-statement or just some.)
-
- Did you read pages S-29 - S-32 (in the English version, anyway) of the
- 4GL 4.1 Supplement document? If so, what was unclear?
-
- > With thanks in advance,
- > Kristjan Gaukur Kristjansson
- > gaukur@rhi.hi.is
-
- --
- Alan Denney aland@informix.com {pyramid|uunet}!infmx!aland
- I says, "Earl, this hill can spill us
- you better slow down or you're gonna kill us
- just make one mistake, and it's the Pearly Gates
- for them 85 crates of U.S.D.A.-approved cluckers.
- You wanna hit second gear, please?"
- -- 'C. W. McCall', "Wolf Creek Pass"
-