Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!pt.cs.cmu.edu!andrew.cmu.edu!bg0l+ From: bg0l+@andrew.cmu.edu (Bruce E. Golightly) Newsgroups: comp.databases Subject: Re: Ingres Endretrieve problems Message-ID: Date: 9 Apr 90 13:41:19 GMT References: <5394@drutx.ATT.COM> Distribution: comp Organization: Carnegie Mellon, Pittsburgh, PA Lines: 23 In-Reply-To: <5394@drutx.ATT.COM> I'm not sure I understand the problem. Can this be addressed using a REPEAT RETRIEVE? If you are only interested in the first row of a set, then there is no particular reason to enter the retrieve loop, as indicated by the ##{ - ##} pair. By using a REPEAT, you incur most of the performance penalty the first time the statement is executed, from then on , performance is considerable better. I use this technique in some of my applications, so I know it works. On a larger scale, though, the problem still exists. Trying to terminate a retrieve loop pre-maturely has some of the same characteristics of having a program fail badly. You are left with an assortment of temp-files lying about that have to be cleaned up by doing a RESTOREDB or PURGEDB. This is a more serious problem because of the disk usage. ############################################################################### ! Bruce E. Golightly ! bg0l@andrew.cmu.edu (BeeGeeZeroEl) Chief of Data Base Development ! (412)268-8560 Telecommunications Group ! Carnegie Mellon University ! UCC 117, 4910 Forbes Ave. ! Pittsburgh PA 15213-3890 Vice President, Western Penna IUA ! ###############################################################################