← Back to team overview

mugle-dev team mailing list archive

Re: Using the persistence Manager many times in one method

 

Basically what you should be doing - if using the Getter classes, is ONLY
pass the PersistenceManager to the call IF you are updating the object once
gotten (ie server side).  If you're just getting the objects from the
datastore, do not pass the call a PersistenceManager pm,  and it the call
will handle it on its own.

On Mon, May 23, 2011 at 1:12 AM, Matt Giuca <matt.giuca@xxxxxxxxx> wrote:

>
> On that note, dont use them in a for loop either;
>> I'm going through and having to change many of the ServerSideImpl to use
>> ModelClass.getObject(key.getID()) rather than ModelClass.getObject(pm, key)
>> so that the server doesnt crash
>
>
> Hmm. This seems very wrong; I thought the point of the persistencemanager
> was to open a long-term connection to the DB.
>
> In that case, I've done the wrong thing in UploadService. I'll fix it so it
> opens a new PM each time it wants to write a file.
>

References