pg.ddx.io  University INGRES on Usenet (1985-1995): threads about Berkeley INGRES, QUEL and EQUEL from comp.databases.ingres, comp.databases and net.database  
help / color / mirror / Atom feed
From: Keith W. Hare <keith@jcc.com>
Subject: Re: ODBC competitors?
Date: 1995/08/23
Message-ID: <DDqLLG.Dx6@jcc.com> (raw)
References: <0kCAeP200jcQ02zls0@andrew.cmu.edu>
	<jameslDDoIwE.LJ3@netcom.com>
	<5sL2hosrnTB@site71.ping.at>

wsog@site71.ping.at (Walter Sommergruber) wrote:
>James Logajan  (jamesl@netcom.com) wrote on 21.08.95
>about "Re: ODBC competitors?":
>
>> Andrew A. Houghton (ah0i+@andrew.cmu.edu) wrote:
>>
>> : Are there any generic ODBC-like competitors out there?  I'm just
>> : learning about ODBC, and it seems that the world has jumped on the
>> : ODBC bandwagon.. doesn't anyone have anything bad to say about it?  Ad
>> : if so, what?
>>
>> There are now a few attempts at ODBC-based API's for other platforms; I
>> haven't really looked them over to make any informed comments on them.
>> The closest "competitor" would be the ANSI standard for embedded SQL.
>
>Could someone provide detailled infos (or where to get them) about this
>ANSI standard for embedded SQL ???

ODBC is an implementation of the almost-completed SQL/CLI ISO standard.  Both the 
SQL/CLI draft standard and ODBC are based on work started by the SQL Access Group (SAG) 
and X/Open.  SQL/CLI is an add-on to SQL-92.  The Editor is currently working to get 
the document to ISO by mid-September so the standard can be officially published by the 
end of 1995.

The difference between SQL/CLI and Embedded SQL (the current SQL standard is ANSI 
X3.135-1992 and ISO 9075:1992) is that embeeded SQL requires a program to be 
preprocessed for a specific implementation of an SQL database.  The goal of SQL/CLI is 
to allow an application be be built with standard calls and dynamically linked to a 
specific implementation.  This will allow tool vendors to ship shrink-wrapped packages 
that will work against any SQL/CLI implementation.

Building an SQL/CLI application means you are working with dynamic SQL.  This is more 
flexible, and more complex than dealing with embedded (static) SQL.  (Of course, you 
can also do dynamic embedded SQL.)

>
>> ODBC is a 'C' API to SQL-only RDBM's for applications running on MS-Windows.
>
>Not SQL-only. It depends on your drivers. There are many available with
>access to (e.g.) DBase-files or even ASCII-files.
>
>>
>> (1) ODBC is very language specific. It is not a protocol, ala X-Windows, but
>> just a late attempt to regulate the 'C' API. All other languages (Smalltalk,
>> Cobol, Fortran, Lisp, APL, Basic, etc. ad nauseum), past, present, and
>> future, need not apply.

SQL/CLI (and ODBC) is a Call Level Interface.  While the interface may look C-like, it 
can be called from any language that supports appropriate external routine calls.  The 
actual compatability with other language is going to depend on the particular 
implementation.  (This all would be much easier if there were a standard for calling 
and parameter passing.)

>>
>> (2) ODBC is very SQL specific. QUEL and all other query languages, past,
>> present, and future, need not apply. And forget object-oriented databases.

Yes, SQL/CLI and ODBC are SQL oriented.  SQL is the only international standard for a 
database query language.  QUEL (and other query languages) had some good points, but 
they are not standard.

The SQL standards committees are currently working on adding Object Oriented 
capabilities to the SQL standard.  As this work is completed, support will be added to 
SQL/CLI.  There are lots of issues to be worked out here.  If you are interested, join 
the SQL standards process. (See the SQL Standards Page at http://www.jcc.com/sql_stnd 
for more information on how the US committee, ANSI X3H2, works.)

And the SQL committees are working with the ODMG committee with a goal of having the 
SQL OO extensions support the ODMG requirements.

>...
>
>> (4) While the world is jumping on the ODBC bandwagon, there have been rumors
>> that Microsoft would jump off in favor of something based on OLE.
>
>Can someone (maybe one from Microsoft) state about this ?
>

I'm not from Microsoft, but my impression is that SQL/CLI & ODBC are complementary 
technologies to OLE.  That is, ODBC would be used underneath OLE for access to data 
objects.

Keith Hare
JCC Consulting, Inc. (http://www.jcc.com)
Member, ANSI X3H2, the US SQL standards committee
http://www.jcc.com/sql_stnd







view thread (16+ messages)  latest in thread

Message-ID: <DDqLLG.Dx6@jcc.com>
Permalink:  ../DDqLLG.Dx6@jcc.com/

 · 


This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox