Simon, Yes, I understand what you are saying. I hope this will clear it up a bit. DBD::ODBC *allows* you to build against the proprietary databases. I can see why some like it, because it's easier to be setup. Yes, it should probably change it's name to DBD::SAPDB, etc. I'll have to think about that one.
However, DBD::ODBC "prefers" to be build against a driver manager and have the driver manager "talk" to the specific driver. That's how it is by default on Win32 and that's why, originally, we included a release of iODBC within the tarball. To *encourage* people to use a driver manager. I'll look into the work involved to rename itself (but that may be difficult or painful) during the Makefile.PL stage. I can honestly say it's a lower priority for me as I think the situation should be handled by utilizing a driver manager. If you build against the driver itself, then caveat emptor... Jeff > -----Original Message----- > From: Simon Oliver [mailto:[EMAIL PROTECTED]] > Sent: Monday, February 04, 2002 4:35 AM > To: Jeff Urlwin > Cc: drewhead; [EMAIL PROTECTED] > Subject: Re: Mutiple ODBC APIs? > > > Jeff, perhaps I have misunderstood what is going on here but it is my > impression that DBD-ODBC is being built against propriety > interfaces that look > like an ODBC API library but in fact will only communicate with a specific > DBMS. One such example is SAP-DB. > > If this propriety build of DBD-ODBC will only work with a > propriety DBMS it is > my opinion that it should not be called DBD-ODBC, instead the > module should be > renamed to reflect its specific purpose, in order to properly describe the > DBD's function and allow the loading of the real DBD-ODBC at the > same time. > > -- > Simon Oliver > > > Jeff Urlwin wrote: > > > > Simon, > > > > You should be able to build DBD::ODBC against a driver manager such as > > unixODBC or iODBC (the assumed way to do it from my > perspective, in fact). > > The driver manager will then talk to SAP DB, etc. > > > > Jeff > > > > > -----Original Message----- > > > From: Simon Oliver [mailto:[EMAIL PROTECTED]] > > > Sent: Friday, February 01, 2002 11:11 AM > > > To: drewhead > > > Cc: [EMAIL PROTECTED] > > > Subject: Re: Mutiple ODBC APIs? > > > > > > > > > I raised this issue with the SAP DB driver (it does a simillar thing > > > apparently). I've had no response from the SAP DB people as yet. > > > > > > IMHO, compiling DBD::ODBC against a proprietry interface should > > > not be allowed > > > without a name change to the module. > > > > > > -- > > > Simon Oliver > > > > > > drewhead wrote: > > > > > > > > I have a properiterary ODBC API that I've compiled > DBD::ODBC for with > > > > a bit of hair pulling and hand holding from someone who had done it > > > > before. :) Works just fine. Now I find that I have a need to > > > > connect to a MsSql server from the same box... in the same perl > > > > program no less! > > > > > > > > I didn't really think it would, but when trying to connect to the > > > > MsSql server uing the properitary API I get a Protocol > error. Can I > > > > compile mutiple APIs into DBD::ODBC (and how)? Can I build > and use a > > > > seperate DBD::ODBC module with an MS compatible ODBC API? Am I > > > > barking up the wrong tree and should look at another method? > > > > -- > > > > [EMAIL PROTECTED] > > > >
