Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!wuarchive!decwrl!shelby!unix!hplabs!hp-pcd!hp-sdd!ncr-sd!iss-rb!otl!loreen
From: loreen@otl.SanDiego.NCR.COM (Loreen Prinz)
Newsgroups: comp.databases
Subject: Re: Asynchronous SQL
Message-ID: <318@iss-rb.SanDiego.NCR.COM>
Date: 20 Mar 90 00:49:33 GMT
References: <2438@ncr-sd.SanDiego.NCR.COM> <745@dgis.dtic.dla.mil> <3510@infmx.UUCP> <779@dgis.dtic.dla.mil> <3585@infmx.UUCP> <4990@rtech.rtech.com> <793@dgis.dtic.dla.mil> <5030@rtech.rtech.com> <5045@rtech.rtech.com> <799@dgis.dtic.dla.mil>
Sender: news@iss-rb.SanDiego.NCR.COM
Reply-To: loreen@otl.SanDiego.NCR.COM (Loreen Prinz)
Organization: NCR Corporation, Rancho Bernardo
Lines: 12

In article <799@dgis.dtic.dla.mil> jkrueger@dgis.dtic.dla.mil (Jon) writes:
>Out-of-order execution of work is a wonderful thing;
>concerns for safety remain valid and necessary at the
>present state of the art; 

With asynch sql the statements themselves get executed in the order 
they are sent to the database server.  The main objective is to free
up the client to perform other functions.  It can then periodically
check to see if the sql statement has been completed.

-Loreen Prinz
 NCR Corporation