Hi Disclaimer: I don't have the ambition to clear this up to you. :)
On Mon, May 17, 2010 at 2:16 PM, rvjcallanan <[email protected]> wrote: ... > A logical class hierarchy would look something like this: > Accounts > -->Users > ---->Years > ------>UserDataSchema > > Yet, according to GAE documentation, this is one big humongous Entity > Group (with Accounts at the root) which would fall over on itself as > local copies are maintained and transaction isolation is enforced. > Is there a reason why you can't have each Account as a root entity? (Instead of having one "bhEG". :) -- 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]<google-appengine%[email protected]> . For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- 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.
