Skip to Content.
Sympa Menu

freetds - Re: [freetds] managing two DBD::Sybase modules

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: Andrew Stanley <astanley AT cs.uml.edu>
  • To: "'freetds AT lists.ibiblio.org'" <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] managing two DBD::Sybase modules
  • Date: Mon, 6 Jan 2003 13:27:17 -0500 (EST)

On Mon, 6 Jan 2003, Lowden, James K wrote:

>
> [musing]
>
> Several people have mentioned the need to use FreeTDS and Sybase's libraries
> at the same time in Perl. At present, that's only possible by using
> DBD::Sybase for Sybase and DBD::ODBC or sybperl for FreeTDS. In limited
> cases, it may be possible to get away with manipulating @INC to manage two
> DBD::Sybase modules, but almost no one wants the administration headaches
> that are sure to follow.
>
> I wonder if there isn't/couldn't be a better way. For example, could the
> namespace and module name of DBD::Sybase be altered at configuration time?
> Could we use Perl namespaces another way, to convert DBD::Sybase into, say,
> DBD::FreeTDS::Sybase?
>
> Seems to me this could also be useful to test upgrades and patches.
>
> Andrew used hackery. Is no mechanism available to make that unnecessary?
>
> --jkl
>
>

Well, I just went through and replaced "DBD::Sybase" with
"DBD::FreeTDS", and similar, the whole way through.

The problem is, the XS and generated .xsi refer directly to DBD::Sybase or
similar, which, in turn, requires compilation time modification (I don't
understand XS thoroughly, but, I would imagine that the package that the
XS refers to must be hardcoded in, or maybe there needs to be some
DynaLoader trickery?)

It took me about 10 minutes, since DBD::Sybase is pretty light on source
files.

Cheers,

-Andrew




Archive powered by MHonArc 2.6.24.

Top of Page