Re: Transaction Set clean does not actually clean

On Fri, 7 Dec 2007 15:59:29 -0800
Mitko Haralanov <[email protected]> wrote:

> That's it! I can use the wrapper for thread safety, keep the ts
> instance around and intercept the ts.clean() calls.

The idea that you offered works perfectly when trying to clean the
transaction set.
However, now I am running against a different problem which I can't
figure out how to solve without opening and closing the database:
Since my application act like a daemon, waiting for rpm requests, the
TransactionSet (when created) locks the database and does not allow any
other application to work with it.
This, of course, is solvable with opening and closing the database but
I remember you mentioning that this should not be done because there
are other things that should be taken care of if done.

Would you mind elaborating on that?
Thank you!

-- 
Mitko Haralanov					 [email protected]
Senior Software Engineer			     650.934.8064
System Interconnect Group		    http://www.qlogic.com

==========================================
Remember, God could only create the world in 6 days because he didn't
have an established user base.