[ Please keep the conversation on the list... ] On Tue, 2004-05-18 at 16:23, Dave Boodman wrote: > ok, thanks for the tips on the commit/rollback. so, i can call it on any > old obj or do i have to (can i) create a special/new obj just to do the > commit/rollback.
You can call it on any object, or as a class method. > i assume it knows what to roll back based on the updates > done for the current invocation of the script? It rolls back everything done on the current database connection since the last time you committed. > also, i know about running -x, i just assumed that if it's committing > somewhere, than in x the problem just wouldn't show up at all. No, that's not correct. If you are seeing this problem regularly, then there is some sequence of actions which will cause it. The only chance you have of coming up with a set of steps to reproduce the problem is to run with -X. Otherwise, you get a different child process every time and you have no idea what series of steps caused the issue. The only kind of problem that will not be reproducible under -X is when you have something that comes directly from the interaction of threads or processes. That doesn't sound like what you're seeing here. - Perrin -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
