marti@ethz.UUCP (Robert Marti) (06/01/89)
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
john@sequent.UUCP (John Vander Borght) (06/03/89)
>From: marti@ethz.UUCP (Robert Marti) > ... > Is any vendor out there > willing to state which operations do implicit commits in their > current implementations? > ... Oracle states in the SQL*Plus Reference Guide Version 2.0 on page 2-33 (Commit) "The following commands also commit changes to the database: ALTER, AUDIT, COMMENT, CONNECT, CREATE, DISCONNECT, DROP, EXIT, GRANT, NOAUDIT, QUIT, REVOKE, and RENAME." I would assume that most if not all of these also commit in embedded-SQL. ----------------------------------------------------------------------------- "Mind over matter excludes golf balls." - Fred Corcoran "If you are shooting under 80 you are neglecting your business; over 80 you are neglecting your golf." - Walter Hagen John Vander Borght, System Analyst [ogcvax,tektronix,pur-ee,ut-sally,decwrl]!sequent!john
jeffl@sybase.Sybase.COM (Jeff Lichtman) (06/03/89)
> 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? No, and I don't think anyone ever will. The module language was an attempt by the ANSI committee to bypass language embedding issues. In SQL 86 (the first standard) they came up with a least common denominator of the major existing systems, and tried to avoid sticky problems. Instead of trying to make embeddings part of the standard, they came up with a whole new abstraction. The embeddings were put in an appendix that wasn't officially part of the standard. SQL 89, a superset of SQL 86, has language embeddings as an official part of the standard. I expect the module language to eventually disappear. --- Jeff Lichtman at Sybase {mtxinu,pacbell}!sybase!jeffl -or- jeffl@sybase.com "Saints should always be judged guilty until they are proved innocent..."
jay@umd5.umd.edu (Jay Elvove) (06/05/89)
In article <16856@sequent.UUCP> john@sequent.UUCP (John Vander Borght) writes: > >Oracle states in the SQL*Plus Reference Guide Version 2.0 on page 2-33 (Commit) > >"The following commands also commit changes to the database: >ALTER, AUDIT, COMMENT, CONNECT, CREATE, DISCONNECT, DROP, EXIT, GRANT, NOAUDIT, >QUIT, REVOKE, and RENAME." > In the newest PC release of ORACLE (v51B), the Reference Guide has been superseded by a much thinner reference manual (2.1) that lists only four of the above commands under the description of COMMIT (page 2-21): CONNECT, DISCONNECT, EXIT, and QUIT. A vague pointer to "Transactions" in the Database Administrator's Guide has been added, however. After a few failed attempts to find further information under that subject heading, I did find a subset of the above (specifically, CREATE and DROP) listed on page 133 of the DBA Guide. Any ideas as to why the information might have changed in going from the SQL Reference Guide to the newer Manual? -- Jay Elvove jay@umd5.umd.edu c/o Academic Software Comp. Sci. Center, Univ. of Md., College Park