Actually, if you're only concerned about restricting the number of connections to the DB, you may be able to use the multi-threaded server capabilities of SQL*Net. Of course, you will need to connect through SQL*Net in your Perl program, even if your Perl program is running on the same machine as your DB. I'm not whether from a licensing perspective they count logical connections, or physical connections. If it's the former, you're still screwed.
-----Original Message----- From: CHEN SEI-LIM [mailto:[EMAIL PROTECTED]] Sent: Monday, 12 November 2001 2:34 PM To: Steven Baldwin; [EMAIL PROTECTED] Subject: Re: forking and DBI Steven Baldwin wrote: > An approach I have found that works *using Oracle* is ... > > Connect Parent > : > : (Do whatever Oracle bits the parent needs to do) > : > In fork routine > Disconnect > Do fork > Reconnect in both child and parent > > If anyone has an alternative to requiring the parent to disconnect before > the fork, and reconnect after, I'd love to see it. > > Steve It has no means. It still makes one connection per process. And we still have to buy enough connections that we need. Sharing $dbh between processes can save our money Because we do not have to buy so many connections.
