RE: Sesame 1.0 released!

Jeen,

> -----Original Message-----
> From: Jeen Broekstra [mailto:jeen@aduna.biz]
> Sent: Thursday, March 25, 2004 3:48 PM
> To: Kingsley Idehen
> Cc: sesame-interest@lists.sourceforge.net; www-rdf-interest@w3.org;
> Swap@aifb.uni-karlsruhe.de; ontoweb-list@informatik.uibk.ac.at
> Subject: RE: Sesame 1.0 released!
> 
> On Thu, 2004-03-25 at 17:58, Kingsley Idehen wrote:
> 
> > Is there any reason why Sesame doesn't use JDBC or ODBC for its SQL
> backend
> > connectivity? I struggle to see the value is scoping this strictly to
> Oracle
> > or MySQL when this product should be DBMS agnostic.
> 
> Ah, but Sesame does use JDBC connectivity. There is a generic RDBMS
> implementation available that is as agnostic to specific DBMS products
> as is possible. 
[Kingsley Idehen] 
Okay, great!

>However, SQL is a standard that comes in eh... several
> flavours. Therefore product-specific specializations are implemented for
> Oracle, Postgres and MySQL.
> 
[Kingsley Idehen] 
What are the specific product specializations for Oracle, MySQL, and
Postgres that you don't believe JDBC covers? Put differently, what feature
of Sesame would fail to work if I used its JDBC data access layer atop
Oracle, MySQL, or Postgres?

I believe the JDBC metadata calls and escape syntax covers most of the
perceived short comings of JDBC or ODBC. But I am happy to be enlightened.

Do note that OpenLink Software develops ODBC and JDBC Drivers for a living
when responding :-) Also beat in mind that we have been developing and
maintaining ODBC Drivers for Oracle, MySQL, Postgres, and many others since
the respective inceptions of JDBC and ODBC.

Kingsley Idehen
OpenLink Software
http://www.openlinksw.com 

> Jeen

Received on Thursday, 25 March 2004 16:37:18 UTC