Nick, there's already a patch that Patrick submitted a couple of months ago that I didn't think to be of high priority for the 0.9.6 and 0.9.7 releases. If I remember correctly, it is included with the upcoming 0.9.9 release. Have a look at the road map for 0.9.9, and I am sure you'll find the bug report/issue I am talking about.
Werner Nick Stuart wrote: > Ok, so how do you folks handle this, or is it not an issue and am I > doing something wrong. > > Basically I just have a collection that is lazy loaded in a long > transaction enabled parent object. What I was intially hoping to do is > to be able to load the parent object, and then later when I had to get > the lazy objects out I would just be able to something like: > > db.begin(); > db.update(parent); > //get lazy objects here.. > db.commit(); > > But that doesn't work as you probably know. So I have to re-load the > parent, and then get all the objects. Now, this doesn't hurt much > since most, if not all the time, it pulls the parent object out of the > cache and continues on. > > But this just feels wrong to me for some reason. Is there anyway for > the lazy collection to use the current transaction that its in? > Instead of trying to use its original transaction it was loaded with? > Maybe we could go through the parent and check for lazy objects and > update their transactions when we call db.update(). > > Any ideas? Suggestions? > > -Nick > > ------------------------------------------------- > If you wish to unsubscribe from this list, please > send an empty message to the following address: > > [EMAIL PROTECTED] > ------------------------------------------------- > > ------------------------------------------------- If you wish to unsubscribe from this list, please send an empty message to the following address: [EMAIL PROTECTED] -------------------------------------------------
