DBD::mysql fork() problem

hello guys,

after upgrading DBD::mysql from 2.1026 to 2.9002 i ran into the problem that after a fork(), the child looses connection to the database.
i've read the discussion on this list about multiple access on a single db handle, but this is how fork() is working. due to internal issues, i cant connect to the database AFTER the fork(). i dont see why this behaviour was changed, as if one just lets the parent die to daemonize a process, things are fine. its how fork() works and if one would not like to have various instances using the same handle, just dont do it this way.

or maybe i just overlook an important reason for it.

regards,
h. steuer




--
This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any unauthorized
copying, disclosure or distribution of the material in this e-mail is strictly
forbidden.

--
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe: http://lists.mysql.com/perl?unsub=gcdmp-msql-mysql-modules@m .gmane.org