pg.ddx.ioUniversity INGRES on Usenet (1985-1995): threads about Berkeley INGRES, QUEL and EQUEL from comp.databases.ingres, comp.databases and net.database
Subject: Re: ODBC competitors?
Date: 1995/08/22
Message-ID: <41cn8s$i8k@knot.queensu.ca> (raw)
References: <0kCAeP200jcQ02zls0@andrew.cmu.edu>
In article <jameslDDoIwE.LJ3@netcom.com> James Logajan <jameslDDoIwE.LJ3@netcom.com>
writes:
>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?
>
>(1) ODBC is very language specific.
> ...
>(2) ODBC is very SQL specific.
> ...
>(3) ODBC is loosely tied to MS-Windows.
> ...
>(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.
Some facts and *my* opinions about ODBC:
(1) the CLI specs in draft version of ANSI-ISO SQL standard(would be
SQL 96) is more or less an ODBC or ODBC is more or less an ANSI-ISO CLI
(especially for ODBC 3.0). The ANSI-ISO CLI is language independent
which can be implemented and called by most(if not all) languages
James Logajan has mentioned. Alos, unlike on of the poster has said,
ODBC is NOT C oriented. For example, the concept of 'not null terminated
sting' in ODBC is introdced for languages other than C such as Cobol, Basic,
etc. I believe most C programmers(at least me) are extremaly 'hate' this
concept. ODBC is not a protocol. The reason ODBC is specified not as
a protocol is, as a standard, it need to allow application to do database
access with and without network involvement. However, driver(2-tier and up)
implementers can use any protocol they like or available.
(2) ODBC actually include two parts. i.e ODBC CLI and ODBC SQL. the ODBC
SQL of cause is very SQL specific. However, ODBC CLI is not. There
are nonSQL driver available (such as ISAM driver) which allows
user to access flat file through ODBC CLI.
(3) Sun and HP will soon bundle an ODBC driver manager with the operation
system(Solaris and HP/UX). That is, when you get the os(i think most
reader know they are unix), you will automaticlly get an ODBC driver
manager(as the standard system library). I believe other unix and
workstation OEM will follow. Many database vendors and third party
companies offer ODBC drivers or Gateway on unix, vms, mainfram, etc
Much samiliar to ANSI CLI which can be said is 100% platform independent
specs, 99% of ODBC is platform independent. gnu iODBC driver manager
(which is a ODBC 2.0 compliant ODBC driver manager) is mainly targeted
for unix platforms and already ported to SunOS, Solaris, HP/UX, UnixWare,
Irix, NCR, Linux ELF, DEC Alpha, etc.
(4) Some database vendors(include Infomix, IBM, Watercom, etc.) have
adopted ODBC as the native CLI for their database engine(s). The reason
is not because of ODBC or at least not because of it only. It is the
first prepared step for adopting ANSI SQL 96 CLI specs. No matter where
microsoft may jumped to, ANSI-ISO specs will be accepted by most
(if not all :) ) database vendors. Thus, if ODBC(esspecially ODBC 3.0)
is a established industral standard and covers(at least
most part of) ANSI-ISO specs, why don't use it before the publication
(and adopt) of the ANSI-ISO specs.
(5) http and html is very close to something described by James --
not language(i mean programming language) specific and be a protocol,
not SQL specific, not tied to mw-windows or other os, not coming from
microsoft -- the http and html. However, when a http server need to
access a local(i.e. on the same mechine) database, it is much efficient
to do a direct CLI access rather than through another protocol
gateway.
Ke