Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • It's coming, I think (Score:3, Interesting)

    by jdavidb (1361) on 2002.05.01 9:21 (#7788) Homepage Journal

    Tim Bunce is working on an Oracle::OCI module. I've never completely understood, but I believe this is Oracle's call level interface as opposed to the preprocessed Pro*C you usually have to use. If it's what I think it is, someone could write a DBD backend using this module (I think that's the plan) and you wouldn't need to install all that junk. I'm not sure, though, if Oracle::OCI needs to link a C library or not.

    If OCI specifies the actual protocol over the wire, it should be completely possible to implement in 100% Perl. At work I've been wishing we could do that with Remedy, but I think you can only get at that system through the provided C library. (For which there is, fortunately, a Perl wrapper.)

    --
    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
  • Your other option is to get the DBA to set up a proxy server and connect via DBD::Proxy.
  • I don't remember specifically how, but I was able to install only the necessary client info (SQL*Plus, Net8 and some other goop I think) on an updated RH 7.1 machine. It was relatively straightforward from the installer, IIRC. Of course, I don't even know enough about Oracle to be dangerous, so YMMV, etc.