http://www.perlmonks.org/?node_id=594175 outlines handling fork cloned db handles. RJ
R P wrote: > Not being a master of perl yet here is what I did: > > I created a module with this at the top to avoid always having to pass > $dbh around: > our $dbh=\$HTML::Mason::Commands::dbh; > > > It worked out pretty well (I think). Then I started to do a fork and > things went badly... AutoCommit errors, Commands out of sync, and when > one module called another I had more problems. What is the proper way > to handle this? > (FYI, I'm forking to do processing on an OpenOffice document and don't > care about the child returning...) > > > TIA!! > > Ryan > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > ------------------------------------------------------------------------ > > _______________________________________________ > Mason-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mason-users > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Mason-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mason-users
