Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!iscuva!iscuvc.iscs.com!bodhi From: bodhi@iscuvc.iscs.com (Satyabodhi) Newsgroups: comp.databases Subject: Re: Do you like your UNIX RDBMS? Message-ID: <2512@iscuva.ISCS.COM> Date: 5 Jun 89 16:24:03 GMT References: <9703@dasys1.UUCP> <3378@fp.sei.cmu.edu> <2907@osiris.UUCP> <427@fdmetd.uucp> Sender: news@iscuva.ISCS.COM Reply-To: bodhi@iscuvc.iscs.com.UUCP (Satyabodhi) Organization: ISC-Bunker Ramo, Spokane WA Lines: 23 In article emuleomo@yes.rutgers.edu (Emuleomo) writes: >The problem with Embedded SQL is that is super lousy for browsing thru' a >database. 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? >Thus your client will be FORCED to wait for up to 5 minutes before he/she >gets a response from a simple query! This is not true with EMPRESS ESQL. With Empress you get the first record right away. >Also, another sore point with a DBMS like ORACLE is that you can't access >a PREVIOUS record. ie. you can't browse backwards. THIS SUCKS!! >Again, in lowly Dbase, all you have to do is SKIP -1. >--- Emuleomo O.O. (Disgusted with Embedded SQL!!) Empress provides a C library interface which allows reading previous record(s). You may not read previous with Empress ESQL. To read backward with ESQL, you issue a fresh select, which inverts your previous order-by clause and limits your selection to what you have already seen. Programs written with ESQL have a chance to be ported to a new DBMS. All C library interfaces are proprietary.