Nevermind, I found the link that describes Transactions as limiting queries as well as updates...
http://code.google.com/appengine/docs/java/datastore/transactions.html#What_Can_Be_Done_In_a_Transaction On Nov 12, 9:51 am, James H <[email protected]> wrote: > 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)" <[email protected]> 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 <[email protected]> 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- Hide quoted text - > > - Show quoted text - -- 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=.
