----- Original Message ----- From: "BAO RuiXian" <[EMAIL PROTECTED]> To: "Michael A Chase" <[EMAIL PROTECTED]> Cc: "ariel mastracchio" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, February 06, 2002 12:03 Subject: Re: Problems DBI/DBD::Oracle/Perl..
> Michael A Chase wrote: > > > I said, a signal handler in the _child_ process. If you have opened the > > database handles in the children (as you should), catching the > > Sorry for interuption, would you tell more about why the database handles should > be openned in the children. I want to know more more about this. I just made > some changes to an Perl/DBI application so that it can run long processes of > executing big SQL statements. The change I made is that the only significant > line in the children is > > $sth->execute(); > > And it works. Maybe it works now. I would not count on it without very extensive testing. Some databases, Oracle in particular, don't behave well with handles passed from parent to child. See InactiveDestroy in the manual (perldoc DBI). -- Mac :}) ** I normally forward private questions to the appropriate mail list. ** Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age.
