My app has a UserProfile class (entity) with many fields. These are your typical user demographics - age, marital status, etc. Over time users will change the fields, i.e. get married or divorced.
I need to keep a history of changes. I am wondering if creating another entity of the entire class containing only the data in the changed field would be efficient. Ignore the mechanics of tracking how the new entity relates to the old since I think that is just detail chasing. The question is whether the new entity with only a single field populated is only the size of that field, or nearly so. Or is the stored entity have a default field for every field in the entity, basically making it as large as the original entity. The other approach would be to keep a name-value pair containing the change in a 'delta' entity. Which would be more efficient in the datastore? Rud http://www.mysticlakesoftware.com -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
