Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!cs.utexas.edu!uunet!mcvax!cernvax!ethz!marti
From: marti@ethz.UUCP (Robert Marti)
Newsgroups: comp.databases
Subject: SQL Standardization
Keywords: module language, implicit commit
Message-ID: <1120@ethz.UUCP>
Date: 1 Jun 89 07:44:54 GMT
Organization: ETH Zuerich
Lines: 25

I have a few questions concerning SQL and especially the ANSI SQL
standardization effort.  Note that my information about ANSI SQL is
taken from Chris Date's book, "A Guide to the SQL Standard" [Date 87].
I have no access to the official standard document.

Specifically, I'd like to know the following:

1. Has any vendor out there (Oracle, RTI, Sybase, ... ) actually
   implemented the module language discussed in [Date 87], Section 3.2,
   as an alternative to embedded SQL?  Is anyone planning to do so --
   and even state this publicly in netnews?

2. Does the standard specify anything about which SQL statements have
   implicit commit?  (For example, in Oracle, the execution of operations
   such as CREATE TABLE, CREATE VIEW, DROP TABLE, DROP VIEW seems to
   implicitly commit all previously uncommited database updates.  This
   is undesirable in some of our applications.)  Is any vendor out there
   willing to state which operations do implicit commits in their
   current implementations?

-- 
Robert Marti                      Phone:      +41 1 256 52 36
Institut fur Informationssysteme
ETH-Zentrum                       CSNET/ARPA: marti%inf.ethz.ch@relay.cs.net
CH-8092 Zurich, Switzerland       UUCP:       ...uunet!mcvax!ethz!marti