Ken Williams wrote: > > [EMAIL PROTECTED] (Jeffrey W. Baker) wrote: > >IMHO Apache::DBI causes more problems than it solves with it's > >"transparent" replacement of DBI functions. Can anyone point to an > >example where a subclass of DBI would not do everything that Apache::DBI > >does, except without the headaches? > > Yes, here's an example: a subclass wouldn't let existing scripts run > *unmodified* with persistent connections. Well, yeah. I think that's the point. In any rational world, you wouldn't expect the loading of a class called Apache::DBI to affect the methods of the class called DBI. Apache::DBI is a weird class. Most people never call any methods from it. For them, the incantation 'use Apache::DBI;' is pure voodoo programming. -jwb
- RE: PerlFreshRestart and %INC Young, Geoffrey S.
- RE: PerlFreshRestart and %INC G.W. Haywood
- RE: PerlFreshRestart and %INC Young, Geoffrey S.
- Re: PerlFreshRestart and %INC Tim Bunce
- Re: PerlFreshRestart and %INC Randal L. Schwartz
- Re: PerlFreshRestart and %INC G.W. Haywood
- Re: PerlFreshRestart and %INC Tim Bunce
- Re: PerlFreshRestart and %INC brian moseley
- Re: PerlFreshRestart and %INC Jeffrey W. Baker
- Re: PerlFreshRestart and %INC Ken Williams
- Re: PerlFreshRestart and %INC Jeffrey W. Baker
- Re: PerlFreshRestart and %INC Chip Turner
- Re: PerlFreshRestart and %INC Andrei A. Voropaev
- Re: PerlFreshRestart and %INC Ken Williams
- Re: PerlFreshRestart and %INC Doug MacEachern
- RE: PerlFreshRestart and %INC G.W. Haywood
- RE: PerlFreshRestart and %INC Young, Geoffrey S.