General question - If I have very large entities with information that varies in usage, should I split the information I use less into another entity?
I'm creating fairly large entities (column wise) and was wondering what the proper strategy was to approach storing the properties. An example is, I'm creating profiles for people. This includes basic information like name, email, url, but also information like bios, interests, affiliations. 90%+ of the time I will not need the bios/interests/affiliations, just the name/email/url. Should I be splitting the larger blocks of information into another entity, and rather than just have a "Person" entity, instead have a "Person" entity AND a "PersonDetails" entity? I arrived at this concern when I was doing queries, and I fear that with loading larger entities I'm consuming too many resources getting each property. Is this something I should be concerned about? Or just query large entities and it won't matter. Thanks! -- 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.
