I recommend this video<http://www.youtube.com/watch?v=AgaL6NGpkB8&playnext_from=TL&videos=geh1T1kPh70> (Youtube Link: http://www.youtube.com/watch?v=AgaL6NGpkB8&playnext_from=TL&videos=geh1T1kPh70 ).
The simple way to avoid loading big property one time is to design the property as owned-relationship<http://code.google.com/appengine/docs/java/datastore/relationships.html> . To keep the consistency between the object in your memory (maybe use memcache) and entity in datastore, it's better to load all properties one time (except for big properties that may cause performance issue). On Thu, Apr 1, 2010 at 8:52 AM, Eli Jones <[email protected]> wrote: > it would be nice to get only a few properties for an entity.. and then > update those entities and the .put() would only need to send the updated > values over the wire -- Best Regards, >From Raymond Ling -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
