On Fri, Jan 10, 2003 at 06:03:31PM -0800, David L. Good wrote: > > I for one think a separate module would be useful. I was working on a > program awhile back where we needed to get data from a MS SQL database and > put it into a Sybase database. I don't remember what we did to get it to > work, but it was a pain in the butt. I suspect there are a number of people > out there with similar issues, especially those migrating to SQL Server from > Sybase or vice versa. An alternative, I suppose, would be a DBD::MSSQL or > some such to specifically address the oddities of MS SQL Server.
That brings a separate issue of being able to have one module compiled and installed twice, against different libraries. In a couple of times I needed to copy data from one version of Oracle to another, and the versions seemed to be especially picky about talking only to the exact versions of Oracle client (Net8) libraries. So I would have appreciated to have DBD::Oracle/8.1.7 and DBD::Oracle/9.0.1 and DBD::Oracle/9.2.0, linked againsts various ORACLE_HOMEs and against various lib/ and lib32/ and lib64/, and be able to make connections with different versions to different datasources. I can imagine that the libraries would refuse to be dynamically loaded twice into one process in the first place. And actually, IIRC I ended up using DBD::Proxy and extra dbiproxy with different PERL5LIB. -- ------------------------------------------------------------------------ Honza Pazdziora | [EMAIL PROTECTED] | http://www.fi.muni.cz/~adelton/ ... all of these signs saying sorry but we're closed ... ------------------------------------------------------------------------
