At 9:28 +0100 6/10/03, Martin Waite wrote:
Hi,
I reworked my code so that my parent process opened the
DBI connection after the child was forked, and
everything works fine. So it looks like Robin is right.
The one thing I don't understand just now is how the
parent automatically re-connected to
Hi,
I reworked my code so that my parent process opened the
DBI connection after the child was forked, and
everything works fine. So it looks like Robin is right.
The one thing I don't understand just now is how the
parent automatically re-connected to MySQL after
the child clobbered the D
L PROTECTED]
> Sent: 09 June 2003 12:10
> To: MySQL List
> Subject: problem with DBI connection interaction with sub-process
>
>
>
>
> What seems to happen is that when the child exits, the
> DBI connection to the database is lost and automatically
> reconnected (how?
really),
Robin Keech
Java Developer
Synectics Ltd
-Original Message-
From: Martin Waite [mailto:[EMAIL PROTECTED]
Sent: 09 June 2003 12:10
To: MySQL List
Subject: problem with DBI connection interaction with sub-process
What seems to happen is that when the child exits, the
DBI
Hi,
Maybe this is a DBI question rather than MySQL, but here
goes...
I have a perl script which forks in order to work around a
memory leak in XML::Parser.
The child parses the data and the parent reads the
results back from the child to populate some temporary
tables in the database.
What se
