ODBC really annoys me! There is NO reason that they couldn't have
proposed a standard wire format instead of just a standard API. We're
all suffering from the stupidity of that missed opportunity.
There are at least two companies that make ODBC drivers and server
side interfaces that can talk to multiple databases (allowing you to
use one client for different back end databases) and one of them even
uses a published protocol. I believe that either the CORBA DB
API or possibly something else like a Java database interface will
eventually win out.
Note that until Java made it necessary (IIOB), Corba also had a fatal
flaw: Corba also didn't propose a wire format for data. That meant
you had to both buy into Corba AND a particular Corba companies
proprietary implementation!
For both of these, I scoured public documents and books for a long
time before I realized this. In both cases, probably intentionally,
this favored a monopoly-like situation where it was difficult to
create your own drivers.
Even just a straight isql (i.e. pure ascii SQL, where binary data is
encoded as hex) interface over a socket would be more than sufficient
to deal with the problem of a standard interface. I've always been
amazed and disgusted at what you have to deal with to talk to a
database.
Believe me, I have Many ideas of ways to solve all of this. ;-)
sdw
> --------------------------------------------------------
> Jacques Gelinas (jacques@solucorp.qc.ca)
> Linuxconf: The ultimate administration system for Linux.
> see http://www.solucorp.qc.ca/linuxconf
> new developments: remote GUI admin, multiple machines admin, wu-ftpd
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu