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 feedODBC competitors?
16+ messages / 7 participants
[nested] [flat]
* ODBC competitors?
@ 1995-08-21 00:00 Andrew A. Houghton <ah0i+@andrew.cmu.edu>
0 siblings, 3 replies; 16+ messages in thread
From: Andrew A. Houghton @ 1995-08-21 00:00 UTC (permalink / raw)
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?
Thanks in advance,
Andrew
^ permalink raw [nested|flat] 16+ messages in thread
* Re: ODBC competitors?
@ 1995-08-21 00:00 jamesl@netcom.com
parent: Andrew A. Houghton <ah0i+@andrew.cmu.edu>
2 siblings, 5 replies; 16+ messages in thread
From: jamesl@netcom.com @ 1995-08-21 00:00 UTC (permalink / raw)
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.
But if you're looking for someone to say something bad about ODBC, I'd be
happy to fill this void by analysing the following statement:
ODBC is a 'C' API to SQL-only RDBM's for applications running on MS-Windows.
(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.
(2) ODBC is very SQL specific. QUEL and all other query languages, past,
present, and future, need not apply. And forget object-oriented databases.
(3) ODBC is loosely tied to MS-Windows. Considerable damage must be done to
the ability to handle multiple simultaneous data source connections in order
to port it to other platforms, such as Unix.
(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.
This is all that I can think of off the cuff. If you want more bad stuff
on ODBC, just ask and I can expand and refine this list.
^ permalink raw [nested|flat] 16+ messages in thread
* Re: ODBC competitors?
@ 1995-08-22 00:00 ebbe@myhost.subdomain.domain
parent: jamesl@netcom.com
4 siblings, 1 reply; 16+ messages in thread
From: ebbe@myhost.subdomain.domain @ 1995-08-22 00:00 UTC (permalink / raw)
James Logajan (jamesl@netcom.com) wrote:
: (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.
Huh? I've been writing ODBC apps in both Pascal and Visual Basic for
a few years now, and haven't seen any 'C'-style restrictions anywhere.
In fact, anyone who can call a Windows DLL can be an ODBC-aware application.
--
Ebbe Jonsson, Systems Mangler ebbe@cardinal.fi
Tel: +358 53 553 53 97 ebbe@dbm.fi
Fax: +358 0 33 88 22 " Why me? "
^ permalink raw [nested|flat] 16+ messages in thread
* Re: ODBC competitors?
@ 1995-08-22 00:00
parent: Andrew A. Houghton <ah0i+@andrew.cmu.edu>
2 siblings, 1 reply; 16+ messages in thread
From: @ 1995-08-22 00:00 UTC (permalink / raw)
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
^ permalink raw [nested|flat] 16+ messages in thread
* Re: ODBC competitors?
@ 1995-08-22 00:00
parent: Andrew A. Houghton <ah0i+@andrew.cmu.edu>
2 siblings, 0 replies; 16+ messages in thread
From: @ 1995-08-22 00:00 UTC (permalink / raw)
In article <jameslDDoIwE.LJ3@netcom.com> James Logajan <jameslDDoIwE.LJ3@netcom.com>
writes:
>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.
Then you mean ANSI embedded SQL is a competitor of ANSI dynamic SQL.
In fact, ANSI-ISO SQL standard includes embedded SQL specs, dynamic SQL
specs(92) and CLI(call level interface) specs(96 draft), etc. And ODBC
standard includes both ODBC (dynamic) SQL and ODBC CLI. To access a
(relational) database (i.e. SQL engine), you need to execute a (dynamic)
SQL query through CLI (either ANSI or ODBC) and retrive query results.
None of the above specs ( embedded sql, dynamic sql and cli) is included
as a competitor of others.
Ke
^ permalink raw [nested|flat] 16+ messages in thread
* Re: ODBC competitors?
@ 1995-08-22 00:00 mcarpentier@techgnosis.com
parent: jamesl@netcom.com
4 siblings, 0 replies; 16+ messages in thread
From: mcarpentier@techgnosis.com @ 1995-08-22 00:00 UTC (permalink / raw)
In article <jameslDDoIwE.LJ3@netcom.com>, jamesl@netcom.com (James
Logajan) wrote:
> 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.
>
> But if you're looking for someone to say something bad about ODBC, I'd be
> happy to fill this void by analysing the following statement:
>
> ODBC is a 'C' API to SQL-only RDBM's for applications running on MS-Windows.
>
> (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.
>
> (2) ODBC is very SQL specific. QUEL and all other query languages, past,
> present, and future, need not apply. And forget object-oriented databases.
>
> (3) ODBC is loosely tied to MS-Windows. Considerable damage must be done to
> the ability to handle multiple simultaneous data source connections in order
> to port it to other platforms, such as Unix.
>
> (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.
>
> This is all that I can think of off the cuff. If you want more bad stuff
> on ODBC, just ask and I can expand and refine this list.
Hello James & Andrew,
A few points.
IMHO, most of the points James mentioned are correct. ODBC is SQL
specific, language specific, loosely tied to MS-Windows, and so on.
However, most of the (end-user and corporate development) world doesn't
care, it does what they want, e.g. attaching an SQL-table in MS-Access.
Nonetheless, since 1987 with SequeLink we have been stressing considerably
the importance of non-SQL connectivity. SequeLink as such does not care
what you use it for; it will (simply) transport your request to whatever
service you're interested in on the other side. E.g. with the SequeLink
Engine you can access non-relational services; the example we provide on
Unix is the Unix Shell Terminal; it allows you to issue a Unix shell
command in your application, and SequeLink returns the result straight in
your app. So, SequeLink itself does not do any "interpretation"; the
service you're accessing will do that.
The origin of this is that we have always used (in case of RDBMS's) the
native SQL of the database in question; so, we have never defined a
standard SQL, which, until the advent of ANSI 92 was a meager subset of
SQL anyway, depriving you of the extra functionalities provided by the
database engine.
Now these kind of features are appreciated by people who really have to go
beyond what the standard (ODBC) connectivity drivers can offer you (we
also support ODBC, also on non-Windows platforms, but it remains your
choice, and we do stress the possibility of pass-through SQL). E.g. there
is an OODBMS vendor which uses SequeLink to provide connectivity to its
database engine, exactly because it does not rely on SQL as such.
If you want to know more, please check out our Web Site at
http://www.techgnosis.com/techgnosis/ or in the US please contact:
TECHGNOSIS INC. - BOSTON
Mr. Marc Shinbrood
One Van De Graaff Drive
MA 01803 Burlington
USA
Tel: +1-617-229 61 00, Fax: +1-617-229 05 57
email: mshinbrood@techg.com
If you would have additional questions or issues, please do not hesitate
to contact Marc or me at any time.
Kind regards,
---------------------------------------------------------------------
Michiel Carpentier | Tel: +32-15-30 77 00
TechGnosis International | Fax: +32-15-32 12 60
A. Stocletlaan 87 | ------------------------------------------
B-2570 Duffel | mcarpentier@techgnosis.com
BELGIUM (*We've moved!*) | http://www.techgnosis.com/techgnosis/
---------------------------------------------------------------------
----- SequeLink, the freedom of choice Client/Server MiddleWare -----
---------------------------------------------------------------------
^ permalink raw [nested|flat] 16+ messages in thread
* Re: ODBC competitors?
@ 1995-08-23 00:00 Keith W. Hare <keith@jcc.com>
parent: jamesl@netcom.com
4 siblings, 1 reply; 16+ messages in thread
From: Keith W. Hare @ 1995-08-23 00:00 UTC (permalink / raw)
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
^ permalink raw [nested|flat] 16+ messages in thread
* Re: ODBC competitors?
@ 1995-08-23 00:00 jamesl@netcom.com
parent: jamesl@netcom.com
4 siblings, 0 replies; 16+ messages in thread
From: jamesl@netcom.com @ 1995-08-23 00:00 UTC (permalink / raw)
Walter Sommergruber (wsog@site71.ping.at) wrote:
: James Logajan (jamesl@netcom.com) wrote on 21.08.95
: about "Re: ODBC competitors?":
[elided]
: > 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.
To form a query on those flat files you still need to use some query language.
In the case of ODBC it is SQL.
[elided]
: > (3) ODBC is loosely tied to MS-Windows. Considerable damage must be done to
: > the ability to handle multiple simultaneous data source connections in order
: > to port it to other platforms, such as Unix.
: Why damage?
Because the Microsoft specification is built with the DOS/Windows architecture
in mind, which includes it's way of handling dynamic linked libraries (DLL's).
All the setup and install DLL functions assume conventions applicable only
to DOS/Windows. Dynamic linking is critical to what makes ODBC more than
the usual run-of-the-mill standard. But dynamically linked libraries either
do not exist for some OS's or exist in many disparate implementations (like
on many variants of Unix).
^ permalink raw [nested|flat] 16+ messages in thread
* Re: ODBC competitors?
@ 1995-08-23 00:00 jamesl@netcom.com
parent:
0 siblings, 0 replies; 16+ messages in thread
From: jamesl@netcom.com @ 1995-08-23 00:00 UTC (permalink / raw)
KeJin wrote:
: 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.
Note: my comments, to which Ke Jin is replying, were directed entirely at
ODBC 2.0. I do not have any information on ODBC 3.0. If you would so kind as
to tell me when the ODBC 3.0 spec came out and relevant purchasing information,
it would be greatly appreciated. The reference document for ODBC 2.0 (at least
the only one that I'm aware of) is:
"Microsoft ODBC 2.0 Programmer's Reference and SDK Guide: for Microsoft
Windows and Windows NT" 1994, Microsoft Corporation, ISBN 1-55615-658-8,
$US24.95, UK21.95, Canada$32.95.
Here is the very first line of the very first section "About This Manual":
"The Microsoft(R) Open Database Connectivity(TM) (ODBC) interface is a C
programming language interface for database connectivity."
No mention of Cobol, Basic, etc. occur in the index. Note the trademark
on the phrase. An oxymoron worth savoring: "Open Database Connectivity(TM)"
Also, the issue of 'not null terminated string' and the way Microsoft chose
to pass strings to their SQLxxx() functions has absolutely nothing to do
with any attempt on their part to be language neutral. If you study the
history of Windows and examine the Windows system calls that require
strings, you find that this is a hold-over from Pascal calling conventions
for strings. (If memory serves me correctly, Microsoft Pascal places
arguments on the stack in reverse order from C. And since Pascal strings
use a length/string convention, rather than the C string/null byte convention,
I think you'll find that layout of Windows SQLxxx() arguments suddenly
makes sense. Microsoft was only making life easy for them, not others!)
: (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.
I think you contradict yourself here. I could be wrong, but just how would
a shrink-wrap application know the correct syntax a-priori to query a
non-SQL driver? One of the points of ODBC is to disengage the app
from the specific engine via a standard query language. I take exception
to the query language chosen (too narrow), but do understand the need for
a standard query language. If you could give me an example of what you
you mean, it would help.
: (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.
The iODBC that you posted (and authored, according to the documentation)
is impressive, although I haven't had a chance to compile and test it.
Unfortunately here is another problem you have: a couple of your header files
appear to be edited copies of the Microsoft headers sql.h and sqlext.h -
these are both copyright by Microsoft. I do not know if you acquired
permission to copy them, but you should have at least edited the comments
and/or re-arranged things more if you did not. I seriously doubt that
you can put them in the public domain via GPL if you or Empress did not
acquire the right to do so.
: (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.
Answer to your last question: because Microsoft owns the trademark to ODBC
and the copyrights to all the header files needed to compile apps, drivers,
and of course the specification of ODBC, it can be expected to defend its
operating system from competitors by denying them the use of its standard
at the most damaging time. (Like when they have been suckered into adopting
it and are vulnerable).
: (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
^ permalink raw [nested|flat] 16+ messages in thread
* Re: ODBC competitors?
@ 1995-08-23 00:00 jamesl@netcom.com
parent: Keith W. Hare <keith@jcc.com>
0 siblings, 1 reply; 16+ messages in thread
From: jamesl@netcom.com @ 1995-08-23 00:00 UTC (permalink / raw)
Keith W. Hare (keith@jcc.com) wrote:
[elided]
: 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.)
ODBC looks 'C'-like because, according the specification published by Microsoft,
it IS. (See one of my earlier posts on this thread for the relevant quoted
admission by Microsoft). I think it is vital that people understand that
Microsoft controls ODBC and realize that while it is built on the concepts
behind CLI, it should not be assumed they are somehow interchangeable.
[elided]
: >> (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.
Minor quibble: SQL is the only dominant query language. The fact that IBM
had something to do with is purely coincidental ;-). SQL, like QUEL, once
did not have a published "open" standard either. QUEL does have a published
standard, just not very well known. Shoot, QUEL even has a published
implementation (University Ingres), not something you can say about SQL.
^ permalink raw [nested|flat] 16+ messages in thread
* Re: ODBC competitors?
@ 1995-08-26 00:00 Keith W. Hare <keith@jcc.com>
parent: jamesl@netcom.com
0 siblings, 1 reply; 16+ messages in thread
From: Keith W. Hare @ 1995-08-26 00:00 UTC (permalink / raw)
jamesl@netcom.com (James Logajan) wrote:
>...
>Minor quibble: SQL is the only dominant query language. The fact that IBM
>had something to do with is purely coincidental ;-). SQL, like QUEL, once
>did not have a published "open" standard either. QUEL does have a published
>standard, just not very well known. Shoot, QUEL even has a published
>implementation (University Ingres), not something you can say about SQL.
>
While SQL has not always had a published standard, it has had been a standard
since 1986 (ANSI X3.135-1986 and ISO 9075-1987). The standard was expanded in
1989 and again in 1992.
The current SQL standard is ANSI X3.135-1992 and ISO 9075-1992.
What is the QUEL published standard?
IBM may have originated SQL, and donated their SQL specification to the
standards process, but they certainly do not control the standards process.
Keith Hare
JCC Consulting, Inc. (http://www.jcc.com)
Member, ANSI X3H2, the US SQL standards committee
http://www.jcc.com/sql_stnd
^ permalink raw [nested|flat] 16+ messages in thread
* Re: ODBC competitors?
@ 1995-08-28 00:00 jamesl@netcom.com
parent: Keith W. Hare <keith@jcc.com>
0 siblings, 1 reply; 16+ messages in thread
From: jamesl@netcom.com @ 1995-08-28 00:00 UTC (permalink / raw)
Keith W. Hare (keith@jcc.com) wrote:
: jamesl@netcom.com (James Logajan) wrote:
: >...
: >Minor quibble: SQL is the only dominant query language. The fact that IBM
: >had something to do with is purely coincidental ;-). SQL, like QUEL, once
: >did not have a published "open" standard either. QUEL does have a published
: >standard, just not very well known. Shoot, QUEL even has a published
: >implementation (University Ingres), not something you can say about SQL.
: >
: While SQL has not always had a published standard, it has had been a standard
: since 1986 (ANSI X3.135-1986 and ISO 9075-1987). The standard was expanded in
: 1989 and again in 1992.
: The current SQL standard is ANSI X3.135-1992 and ISO 9075-1992.
: What is the QUEL published standard?
Try "The INGRES Papers" Stonebraker ed. Addison Wesley.
Ingres Corporation/ASK/CA/?? obviously sold an honest to god QUEL engine.
I'm sure they must have published the specification. Wouldn't have
been much of a product without one. (And it was considered the
competitor to SQL in the early to mid 80's). I do recall using it
a few years back....
^ permalink raw [nested|flat] 16+ messages in thread
* Re: ODBC competitors?
@ 1995-08-29 00:00 Keith W. Hare <keith@jcc.com>
parent: jamesl@netcom.com
0 siblings, 0 replies; 16+ messages in thread
From: Keith W. Hare @ 1995-08-29 00:00 UTC (permalink / raw)
jamesl@netcom.com (James Logajan) wrote:
>: What is the QUEL published standard?
>
>Try "The INGRES Papers" Stonebraker ed. Addison Wesley.
>Ingres Corporation/ASK/CA/?? obviously sold an honest to god QUEL engine.
>I'm sure they must have published the specification. Wouldn't have
>been much of a product without one. (And it was considered the
>competitor to SQL in the early to mid 80's). I do recall using it
>a few years back....
>
Sounds like a propriatary vendor language to me. As far as I know, Ingres
was the only implementation of QUEL. QUEL may have been a competitor to SQL
in the early 1980's, but by 1985 SQL had a significant mindshare, if not a
market share.
I think that having a published, public standard for SQL has a lot of
weight.
You can argue about the technical superiority of other database languages,
but at this point SQL is the only dejure standard, and there is nothing else
that is even approaching being a defacto standard.
Keith Hare
JCC Consulting, Inc. (http://www.jcc.com)
^ permalink raw [nested|flat] 16+ messages in thread
* Re: ODBC competitors?
@ 1995-09-04 00:00 Brandon Brown <brando@internetMCI.com>
parent: ebbe@myhost.subdomain.domain
0 siblings, 0 replies; 16+ messages in thread
From: Brandon Brown @ 1995-09-04 00:00 UTC (permalink / raw)
jamesl@netcom.com (James Logajan) wrote:
> How very odd - the only publication that I have ever come across that details
> the ODBC specification contains nothing BUT 'C' function prototypes. What
> you are using isn't ODBC as it is specified by Microsoft. Try this test:
> go down to one of your better local bookstores and try to find the book
> or publication that details the Pascal or Visual Basic ODBC specifications.
>
> Chances are that the ONLY place you can find the specification for ODBC
> for Pascal/Visual Basic is by purchasing a software library. If you can
> get the specifications independent of having to purchase software, then
> it qualifies as a specification, otherwise it is a proprietary front-end.
>
I don't get it. Windows was written in 'C' yet many languages can
make calls to the Windows API. I sure that in the Windows API manuals
that the calls are listed in 'C' with the old FAR PASCAL designations.
I started in 'C' and move to Visual Basic for the front-end develop-
ment and have purchased many libraries, including ODBC libraries.
Not all have Visual Basic VBXs or special "proprietary" functions
have to be called from VB. Many languages can use these libraries,
which to me, questioning your reasoning on using the term
"proprietary"?
Brandon Brown
brando@internetMCI.com
^ permalink raw [nested|flat] 16+ messages in thread
* Re: ODBC competitors?
@ 1995-09-05 00:00
parent: jamesl@netcom.com
4 siblings, 1 reply; 16+ messages in thread
From: @ 1995-09-05 00:00 UTC (permalink / raw)
In article <jameslDDoIwE.LJ3@netcom.com>, jamesl@netcom.com says...
>
>ODBC is a 'C' API to SQL-only RDBM's for applications running on MS-Windows.
>
False. An ODBC driver can mate with any database. For instance, there are
ODBC drivers for RMS on the VAX which is not a relational model.
>(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.
False. ODBC can be accessed from any language which can call a DLL. That
includes VB, COBOL, FORTRAN and others.
>
>(2) ODBC is very SQL specific. QUEL and all other query languages, past,
>present, and future, need not apply. And forget object-oriented databases.
False. ODBC is a SQL front end, but the underlying technology can be any type.
See above RMS example.
>(3) ODBC is loosely tied to MS-Windows. Considerable damage must be done to
>the ability to handle multiple simultaneous data source connections in order
>to port it to other platforms, such as Unix.
What does this mean? I can attach multiple connections to, for instance,
ORACLE on an ALPHA box running OSF/1.
>
>(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.
I don't know if there is any truth to this statement, but if everyone else jumps
on the bandwagon, it won't matter anyway.
>This is all that I can think of off the cuff. If you want more bad stuff
>on ODBC, just ask and I can expand and refine this list.
>
--
The opinions expressed in this message are my own personal views
and do not reflect the official views of Microsoft Corporation.
^ permalink raw [nested|flat] 16+ messages in thread
* Re: ODBC competitors?
@ 1995-09-07 00:00 caelus@comtch.iea.com
parent:
0 siblings, 0 replies; 16+ messages in thread
From: caelus@comtch.iea.com @ 1995-09-07 00:00 UTC (permalink / raw)
: >
: >(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.
: I don't know if there is any truth to this statement, but if everyone else jumps
: on the bandwagon, it won't matter anyway.
Fact is that OLE will simply wrap ODBC!
--
------------------------------------------------------------------
Caelus, Inc. ! Integrated Business Solutions!For info call:
1100 Paulsen Ctr! for Mfg Companies Today !Phone:509-455-8566
Spokane,WA 99201! (HP-UX, OSF-1, AIX) !Fax: 509-634-9794
------------------------------------------------------------------
"When I die, I want to go peacefully like my Grandfather did, in his sleep.
Not screaming like the passengers in his car!"
- Buffy
^ permalink raw [nested|flat] 16+ messages in thread
end of thread, other threads:[~1995-09-07 00:00 UTC | newest]
Thread overview: 16+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1995-08-21 00:00 ODBC competitors? Andrew A. Houghton <ah0i+@andrew.cmu.edu>
1995-08-21 00:00 ` jamesl@netcom.com
1995-08-22 00:00 ` ebbe@myhost.subdomain.domain
1995-09-04 00:00 ` Brandon Brown <brando@internetMCI.com>
1995-08-22 00:00 ` mcarpentier@techgnosis.com
1995-08-23 00:00 ` Keith W. Hare <keith@jcc.com>
1995-08-23 00:00 ` jamesl@netcom.com
1995-08-26 00:00 ` Keith W. Hare <keith@jcc.com>
1995-08-28 00:00 ` jamesl@netcom.com
1995-08-29 00:00 ` Keith W. Hare <keith@jcc.com>
1995-08-23 00:00 ` jamesl@netcom.com
1995-09-05 00:00 `
1995-09-07 00:00 ` caelus@comtch.iea.com
1995-08-22 00:00 `
1995-08-23 00:00 ` jamesl@netcom.com
1995-08-22 00:00 `
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