What you're doing is dangerous already on Linux/Unix. Not all DBDs support fork() on Unix. You take care to disconnect, which might prevent most of the problems. On Windows, fork() is only emulated through threads, and thus, all of the caveats in the DBI documentation about threads apply there. You should have one (and only one) DBI connection in your process. If you want to do parallel processing using a database (which I doubt will be efficient), then I recommend you launch separate child processes through system(1, ...) or system("start $cmd") to have really separate DBI handles.
In reply to Re: DBI and fork() on Win32
by Corion
in thread DBI and fork() on Win32
by FloydATC
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |