From: Dick Davies <rasputnik@...>
Date: 2004-02-24T02:21:11+09:00
Subject: Re: Calling JDBC from with Ruby

Michael Davis wrote:

> dhtapp wrote:
> 
>> "Michael Davis" <mdavis@sevasoftware.com> wrote in message
>> news:AKo_b.4954$yZ1.1140@newsread2.news.pas.earthlink.net...
>>
>> {snip...}
>>
>>
>>> No.  The data that I need to access may not always be relational and I
>>
>>
>> have been given specific requirements for using both JDBC and ODBC.  I
>> explored many possible options for accessing data with my client and they
>> have several very good reasons for these requirements.


> If adding JDBC means using an 
> approach that too difficult to support, I will have to re-write using Java.

Yuk.

Have I missed something here? JDBC is a SQL driver. Why don't you just 
use Rubys SQL support to talk to the database.

I know you said it has 'good reasons' to be JDBC - is that because
there is some custom db that only has a jdbc / odbc facade?
If you can't say, fair enough.