Interesting! Thanks, that's helpful. On Mar 25, 2:19 pm, "Max Ross (Google)" <maxr+appeng...@google.com> wrote: > We could perhaps be a bit more precise in our language here. You can run > any query you want inside a transaction but the results are only guaranteed > to be transactionally consistent if the query is an ancestor query. In > other words, begin/commit are no-ops for non-ancestor queries. > > Here's the history of it: > We considered throwing an exception, but the problem was that when we first > launched we didn't support transactional queries of any sort. We concluded > that requiring developers to step around transactions any time they wanted > to issue a query was a pretty heavy burden, so we decided to ignore active > transactions for all queries. Then, once we figured out how ancestor > queries could participate in a transaction, there was no way to go back > because if we started throwing exceptions for non-ancestor queries in > transactions existing apps would break when we pushed a new SDK to the > back-ends. > > Hope that helps, > Max
-- 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=en.
