If you are only wanting to do this because you don't think your original wrapper is as carefully designed as the rest of your project -- AND you will only be changing the internals and not the API -- then no, i don't see very much value in changing it.
Aside from that, i also see very little value in writing a wrapper or subclassing DBI in the first place.* There are helper modules out there to handle config data, and i have never needed to retry connecting to the database myself. YMMV of course, but i like DBI straight out of the box.
* update: renodino explains this point better than i did. renodino++
jeffa
L-LL-L--L-LL-L--L-LL-L-- -R--R-RR-R--R-RR-R--R-RR B--B--B--B--B--B--B--B-- H---H---H---H---H---H--- (the triplet paradiddle with high-hat)
In reply to Re: Subclassing DBI instead of wrapping
by jeffa
in thread Subclassing DBI instead of wrapping
by spq
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |