Re: Class::DBI over DBD::AnyData - solved?

[prev] [thread] [next] [Date index for 2004/11/27]

> Date: Sat, 27 Nov 2004 00:13:50 +0000
> From: Tim Bunce <Tim.Bunce@xxxxx.xxx>
>
> On Fri, Nov 26, 2004 at 06:28:06PM -0500, Dan Friedman wrote:
> > 
> > Now I have what I wanted: the DBD doesn't support prepare_cached,
>
> Drivers don't: prepare_cached is a service provided by the DBI.

Er. Right. Poor choice of words. Mea culpa. I meant "the driver doesn't do
whatever's required so that I don't have to deal with this."

> > 
> > However, I'm concerned that the techniques I've used to accomplish this are Bad
> > Ideas.
>
> Yeap.
>
> > OTOH, is this something others would find useful? I'm still happy to
> > hear of less hackish solutions to deal with this, but in the meantime, I'm
> > tempted to try all (or many of) the Class::DBI tests out on it and see if I can
> > publish it as Class::DBI::AnyData. Thoughts? Suggestions? Encouragement?
> > Discouragement?
>
> Finding and fixing the actual cause seems better than assorted hacks
> to avoid the warning.
>
> Seems like the Active attribute isn't getting reset. Probably means
> the finish() methods isn't working right. Take a look. Use DBI trace().

Excellent, thanks for the pointers. I guess it's time to buckle down and learn
how DBD's actually do their thing.

> p.s. You only said "*seems* to produce warnings about active statement handles"

Again, poor choice of words. Hopefully my meaning was clear.

> and didn't give the version numbers of the relevant modules (Class::DBI and
> DBD::AnyData, at least).

Woops! 

DBD::AnyData 0.08
Class::DBI 0.96
Ima::DBI 0.33
DBI 1.43

Again, thanks for the suggestion.

Cheers,
Dan