I have a strange problem where a database handle is being destroyed for no
apparent reason. My initial idea was to parse some xml, and translate it
into a database. Deleting line after line of code I came up with this short
meaningles program which exhibits the same behavior as its real-life
si
Please don't cross post.
Peter Rabbitson wrote:
> I have a strange problem where a database handle is being destroyed for no
> apparent reason. My initial idea was to parse some xml, and translate it
> into a database. Deleting line after line of code I came up with this short
> meaningles prog
> > If I run the real program I end up stuffing about 480 out of roughly 510
> > products into a designated table and then the handle goes out to lunch with
> > the same error message.
>
> What's the error message?
>
Ups... I guess I missed that:
~$ ./test > /dev/null
Issuing rollback() for dat
Peter Rabbitson wrote:
>>>If I run the real program I end up stuffing about 480 out of roughly 510
>>>products into a designated table and then the handle goes out to lunch with
>>>the same error message.
>>
>>What's the error message?
>>
>
>
> Ups... I guess I missed that:
>
> ~$ ./test > /dev/
> Thank you. No guarantees, but try setting 'InactiveDestroy' when you
> create the DB handle. XML::Twig uses a fork/exec call in 'parseurl' to
> retrieve the URL in one process and to parse the XML in the other. When
> the retrieval is complete one of the processes closes with an 'exit'. I
> think
Peter Rabbitson wrote:
>>Thank you. No guarantees, but try setting 'InactiveDestroy' when you
>>create the DB handle. XML::Twig uses a fork/exec call in 'parseurl' to
>>retrieve the URL in one process and to parse the XML in the other. When
>>the retrieval is complete one of the processes closes wi
Just to sum up the discussion as it was extremely helpful and educational:
> > Hm... I get it and I don't get it... Who keeps the sub _dummy - the parent
> > or the child? I need to use DBI in it so I guess InactiveDestroy must be set
> > to true there. How do I find out who is who not at the time
