Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pasteur!ames!haven!vrdxhq!daitc!daitc.daitc.mil
From: jkrueger@daitc.daitc.mil (Jonathan Krueger)
Newsgroups: comp.databases
Subject: Re: Do you like your UNIX RDBMS?
Message-ID: <530@daitc.daitc.mil>
Date: 31 May 89 12:32:57 GMT
References: <9703@dasys1.UUCP> <3378@fp.sei.cmu.edu> <2907@osiris.UUCP> <May.26.10.00.53.1989.196@yes.rutgers.edu> <427@fdmetd.uucp> <May.30.18.32.22.1989.943@yes.rutgers.edu>
Sender: jkrueger@daitc.daitc.mil
Reply-To: jkrueger@daitc.daitc.mil (Jonathan Krueger)
Organization: DTIC Special Projects Office (DTIC-SPO), Alexandria VA
Lines: 11
In-reply-to: emuleomo@yes.rutgers.edu (Emuleomo)

In article <May.30.18.32.22.1989.943@yes.rutgers.edu>, emuleomo@yes (Emuleomo) writes:
>The problem with Embedded SQL is . . .
>Suppose you issue a query and there are 1000 matching records.
>Are you aware that ALL the current ESQL implementations require that you
>WAIT FOR THE 1000 RECORDS TO BE FOUND EVEN BEFORE YOU CAN VIEW THE 1ST ONE?

This is incorrect.  One extant counter-example is RTI INGRES.
Doubtless there are others.

-- Jon
--