Nick, can you please keep me informed about any progress you make wrt to CASTOR-818, as I did originally plan to start looking into this again (as it's on the road map for 0.9.9). Just trying to make sure that we don't work on the same issue simultaneously ...
Thanks Werner Nick Stuart wrote: > That does look like the same issue I'm talking about. Glad to see its > been spotted already. :) > > I may be able to take a look at the patch and see what needs to be > changed (if anything) for the current CVS CO, but will have to wait > till next week. > > -Nick > > On 7/22/05, Patrick van Kann <[EMAIL PROTECTED]> wrote: > >>Hi nick, >> >>I noticed this a while back and made an attempt to fix it: >> >>http://jira.codehaus.org/browse/CASTOR-818 >> >>I think this describes the situation you are encountering. >> >>Unfortunately I have been too busy to finish what I started. It might be >>worth you having a look at the patch and seeing if it can be resurrected for >>0.97. >> >>Patrick >> >> >>-----Original Message----- >>From: Nick Stuart [mailto:[EMAIL PROTECTED] >>Sent: Fri 22/07/2005 13:25 >>To: user@castor.codehaus.org >>Subject: [castor-user] [JDO] Lazy loading questions.. >> >>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] > ------------------------------------------------- > > ------------------------------------------------- If you wish to unsubscribe from this list, please send an empty message to the following address: [EMAIL PROTECTED] -------------------------------------------------
