(Ovid) Re(2) 1: Committing database transactions with DESTROY

Reading through those threads, what I'm getting is the impression that Generic::Database::DESTROY can be garbage collected before Generic::Database::Modify objects are being collected, thus ensuring that there is no DESTROY method to inherit from. Is this correct? If so, this would explain some of the inconsistent results that I have been getting.

Cheers,
Ovid

Vote for paco!

Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.

Comment on (Ovid) Re(2) 1: Committing database transactions with DESTROY

Replies are listed 'Best First'.
Re (tilly) 3: Committing database transactions with DESTROY by tilly (Archbishop) on Oct 16, 2001 at 23:30 UTC
I think it more likely that your database handle is cleaned up before you destroy $self. Which makes your commit fail.	[reply]