Re: using DBI handles managed elsewhere

[prev] [thread] [next] [Date index for 2005/04/04]

On Mon, Apr 04, 2005 at 03:03:11PM -0400, Perrin Harkins wrote:
> On Fri, 2005-03-25 at 10:00 -0500, Chris Winters wrote:
> > I'm trying to find a good balance here and I'm not sure how much the
> > features from Ima::DBI (primarily caching, yes?) are worth rejiggering
> > an existing infrastructure to wedge it in.
> 
> You can't use Class::DBI without Ima::DBI at this point.  Ima::DBI
> should not be an issue for integrating with OpenInteract2.  You just
> need to override db_Main, which you have to do anyway to use Class::DBI
> with mod_perl.
> 
> The problem I ran into is that modifying an already open handle (which
> you will be getting from OI2) to have a RootClass of
> DBIx::ContextualFetch doesn't seem easy to do, and doing it may cause in
> the rest of your application, because it changes the behavior of
> standard DBI methods in certain contexts.  AFAIK though, the only
> relevant change is that calls to $sth->fetch() in list context behave
> differently, and this may not matter because that would have been a
> strange thing to do before.
> 
> I didn't try very hard before postponing dealing with this problem, so
> maybe we can solve it.

I think Class::DBI can (and should) be altered to not depend on
DBIx::ContextualFetch. It would mean duplicating some DBIx::ContextualFetch
functionality within Class::DBI. It's not much code and, to my mind, the
benefits outweigh the philosophical concerns.

Tim.