in reply to DB-independent wrapper on DBI

Hmm, looks like a recode of DBIx::Connect

Also see DBI database connection support and more

Finally, the term "wrapper" usually means something that abstracts the prepare-execute-fetch cycle, not something that abstracts the connect aspect... but I guess we could use the term more generically.

Carter's compass: I know I'm on the right track when by deleting something, I'm adding functionality.

Replies are listed 'Best First'.
Re: Re: DB-independent wrapper on DBI
by dragonchild (Archbishop) on Oct 16, 2003 at 13:26 UTC
    Yes, it mostly is. One difference is that I handle DBD::Sybase/FreeTDS connections without needing a .freetds.conf file entry. The idea here is that there are a few select databases a number of developers might need to get to, from any system. (There are over 50k different machines where I work.) By handing them one file, they can reach any of these databases. (Of course, assuming the right pre-requisites are installed, which they mostly are.) If I were to recode this, I would use DBIx::Connect, now that I know of it.

    ------
    We are the carpenters and bricklayers of the Information Age.

    The idea is a little like C++ templates, except not quite so brain-meltingly complicated. -- TheDamian, Exegesis 6

    ... strings and arrays will suffice. As they are easily available as native data types in any sane language, ... - blokhead, speaking on evolutionary algorithms

    Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.

[reply]

In Section Code Catacombs