Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!dimacs.rutgers.edu!mips!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!llustig!objy!server!bobm From: bobm@server.Berkeley.EDU (Bob Muller) Newsgroups: comp.databases Subject: Re: Embedded SQL and C Message-ID: <1991Apr25.200437.29570@objy.com> Date: 25 Apr 91 20:04:37 GMT References: Sender: bobm@server (Bob Muller) Reply-To: bobm@objy.com Distribution: usa Organization: Objectivity, Inc. Lines: 26 ANSI X3.168-1989, Database Language--Embedded SQL specifies the syntax and semantics for the precompiled language used to embed SQL statements, to declare variables used in those statements from the program (both input and output), and to handle exceptions raised during execution of the statements. It specifies the syntax for Ada, C, COBOL, FORTRAN, Pascal, and PL/1. There is a lot of stuff about the language-specific data types and their correspondence to the standard SQL data types. ANSI X3.135-1989, Database Language--SQL with Integrity Enhancement, provides for the various ways of specifying bound variables, indicator variables, and similar constructs, and there are some references between the standards. The draft SQL2 standard, X3.194-199x, integrates both standards. As a side benefit, it also adds MUMPS support to the standard (immunization is advised :-). This standard resolves a bunch of semantics issues with the embedded syntax and is more correct if not clearer than the previous standards. None of these standards are particularly well implemented by DBMS vendors at the moment. Most vendors supply a proprietary functional interface to the DBMS; some supply an embedded syntax based on DB2, which is not exactly the same as the ANSI syntax. The DB2 documentation often appears cited as a practical standard. -- -- Bob Muller Objectivity, Inc. bobm@objy.com