On Thu 08 Aug 2002 13:52, "Jeff Urlwin" <[EMAIL PROTECTED]> wrote:
> 
> I'd like to gather some wisdom from the list here.  I have a situation where
> my dbh is being destroyed before the sth is being destroyed and the sth
> doesn't have enough information anymore as the imp_dbh structure is being
> re-used/over-written before the sth is destroyed.  Since the information in
> the imp_dbh is already being over-witten (which may be in DBD::ODBC or may
> be from perl itself), the imp_sth has no real way of detecting this and
> attempts to "clean up" where it can't.
> 
> I know DBI has the notion of counting the kids, but I can't seem to find any
> way to list the existing statement handles to close them, or do I have to do
> that myself?
> 
> Does anyone else have this problem?

Yep. Me. (DBD::Unify)

I've had discussions with Tim too. I finally approached it inside the DBD.
Look at the source code if you wanna know what I did. I've documented it more
than I'm used to :)

HTH

functions to look at (and where and how they are called) in
dbdimp.ic and dbdimp.h

        /* Until those babys are able to change their own dirty nappies ... */
        static void change_offspring (SV *dbh, imp_dbh_t *imp_dbh)

        static void dbd_st_diaper (imp_dbh_t *imp_dbh, imp_sth_t *imp_sth)

        static void dbd_st_growup (imp_dbh_t *imp_dbh, imp_sth_t *imp_sth)


-- 
H.Merijn Brand        Amsterdam Perl Mongers (http://amsterdam.pm.org/)
using perl-5.6.1, 5.8.0 & 632 on HP-UX 10.20 & 11.00, AIX 4.2, AIX 4.3,
     WinNT 4, Win2K pro & WinCE 2.11 often with Tk800.024 &/| DBD-Unify
ftp://ftp.funet.fi/pub/languages/perl/CPAN/authors/id/H/HM/HMBRAND/


Reply via email to