Re: DBI InactiveDestroy problem

See if there are more database handles than you realize open. You can check this with the ChildHandles method described in the DBI docs.

Comment on Re: DBI InactiveDestroy problem

Replies are listed 'Best First'.
Re^2: DBI InactiveDestroy problem by mifflin (Curate) on Dec 02, 2006 at 23:45 UTC
I could try that when I get back into work on monday but I've distilled the problem down to the code you see above. What you see is the entire program and I only do one prepare. If I reconnect and reprepare after the waitpid the errors go away. I was hoping to not have to do that.	[reply]
Re^3: DBI InactiveDestroy problem by perrin (Chancellor) on Dec 03, 2006 at 17:38 UTC
Hmm, try setting InactiveDestroy before you fork.	[reply]