JDBC instead of ODBC
Júlio César Ködel
kodel at terra.com.br
Sat Oct 4 16:17:00 CDT 2003
Easier than a ODBC/JDBC/whateverDBC engine is a custom engine for a specific
database. For example, FireBird (or Interbase 6, which is almost the same),
there is a VB OCX and some LIBs for C to direct connect to Firebird servers
without using ODBC... The most right would we achieve the maximum
information (and source codes) of determined engine and then give it to
Revolution developers... This way, I think new native engines for Revolution
will be more easy made than we just ask "I need a driver for sbrobow
database engine" ;-)
And there is a advantage in this process: as native database engines doesn't
work uppon ODBC, and considering that all database servers are equal
(plataform independent), a engine made for revolution would work in any
plataforms (different from ODBC, which is a problem in MacOS and, I guess, a
really pain in *nix stations).
By the way... Some developer wants the source code for some libs to
----- Original Message -----
From: "Bernard Devlin" <revolution at knowledgeworks.plus.com>
To: <use-revolution at lists.runrev.com>
Sent: Friday, October 03, 2003 4:50 PM
Subject: Re: JDBC instead of ODBC
> >>But what about all those database engines that can use JDBC?
> Todd, maybe you are thinking of things in the converse. Are you seeing
> Rev stacks as databases, and asking for a JDBC driver so that people could
> connect to a stack from a Java application? That is the only sense in
> which the databases you mention have JDBC drivers - so that Java
> applications can connect to them.
> Rev uses ODBC in the opposite way - that is, so that Rev _applications_
> can connect to these _other_ databases.
> The Rev drivers for Oracle, MySQL, Valentina etc. are the Rev equivalents
> of the JDBC drivers - drivers which enable an application to make direct
> (network) calls to a database (that may be local) from within the
> With the databases you cite, the JDBC drivers are provided (effectively)
> by the database providers to enable Java applications to communicate with
> their DB.
> As for Rev apps, there is only really three ways to interface with an
> external database:
> 1) the Runrev-supplied drivers
> 2) ODBC (or maybe a JDBC-ODBC bridge, although usually they are the other
> way round)
> 3) Shelling out to a command line SQL processor
> I expect some more imaginative individual may come up with others....
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Esta mensagem foi verificada pelo E-mail Protegido Terra.
> Scan engine: VirusScan / Atualizado em 01/10/2003 / Versão: 1.4.0
> Proteja o seu e-mail Terra: http://www.emailprotegido.terra.com.br/
More information about the use-livecode