I was under the impression that transaction updates could only occur to 1 Entity Group at a time and I understand that. But, it appears during the transaction we also can NOT read another Entity Group...is that correct?
If so, that seems to be quite limiting to NOT be able to collect information from other Entity Groups A, B (ie reads) in preparation for the update to the targeted Entity Group C. Am I missing something? J On Nov 10, 4:37 pm, "Ikai L (Google)" <ika...@google.com> wrote: > James, > > For all practical intents and purposes, there are no limits on the number of > entity kinds per entity group or limits imposed by the underlying physical > hardware. > > On Fri, Nov 6, 2009 at 6:56 PM, James H <james.hollier...@gmail.com> wrote: > > > Is there any limit on number of entity kinds per entity group or any > > limit on amount of physical storage consumed by a single entity group? > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=.
