From: Kent Sibilev Date: 2004-07-17T02:48:16+09:00 Subject: Re: scripting language (fwd) Long time ago I wrote a oracle client module using Ruby/DL which connected to oracle via Oracle OCI API. There was also a DBD wrapper for this module, so I could use it via DBI interface. So if you do not have a compiler installed but you have Oracle client installed, you can use this module. At that time I tested it only on my WinXP box, and since this is the pure ruby module there are some performance drawbacks as well. URL: http://rubyist.homeunix.net/rubyoci-0.1.tar.gz Cheers, Kent. On Jul 15, 2004, at 6:58 PM, Jamis Buck wrote: > Gavin Sinclair wrote: >> On Friday, July 16, 2004, 5:25:47 AM, Jamis wrote: >>> What I would like is to remove the Oracle client as a dependency, >>> just >>> as the Oracle JDBC (thin) client does. The thin (as opposed to the >>> oci) >>> Oracle JDBC client implements in pure Java the network protocols that >>> communicate with the Oracle database server. >>> This means that the thin client will ultimately be less responsive >>> than >>> the oci client, but its GREAT for working on your own machine. >>> I'm hoping that something like this can be written for Ruby, in Ruby, >>> without the need to create an extension module in C to bridge into >>> the >>> Oracle OCI stuff (which is what the current ruby oracle module does). >> Couldn't the thin client be written in C and then wrapped in every >> scripting language imaginable? If so, *is* there an Oracle thin >> client library written in C already? >> Gavin > > The client *could*, of course be written in C. To my knowledge, such > an implementation does not exist. (Might be a neat project, in fact.) > > However, that still doesn't address the OP's original concern: lack of > a compiler made a C extension impractical. A *pure Ruby* > implementation would still be most convenient, though not as > efficient. > > -- > Jamis Buck > jgb3@email.byu.edu > http://www.jamisbuck.org/jamis > > "I use octal until I get to 8, and then I switch to decimal." >