Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?
 
PerlMonks  

Re: Unexpected and uncatchable database corruption errors using DBD::SQLite & Parallel::ForkManager

by moritz (Cardinal)
on Apr 05, 2014 at 05:40 UTC ( #1081216=note: print w/ replies, xml ) Need Help??


in reply to Unexpected and uncatchable database corruption errors using DBD::SQLite & Parallel::ForkManager

I don't know if this applies to SQLite, but many database systems have a problem if you fork after connecting; In this case, forking first and then connecting to the database (or if that's not an option, reconnect in the child process after fork) is the proper solution.


Comment on Re: Unexpected and uncatchable database corruption errors using DBD::SQLite & Parallel::ForkManager
Replies are listed 'Best First'.
Re^2: Unexpected and uncatchable database corruption errors using DBD::SQLite & Parallel::ForkManager
by djerius (Beadle) on Apr 06, 2014 at 19:14 UTC
    That does the trick. Giving each forked process its own database handle makes all of the corruption errors go away.

    Thanks!

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1081216]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others imbibing at the Monastery: (16)
As of 2015-07-28 21:25 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...









    Results (259 votes), past polls