As I understand it, you can't run a non-ancestor query in a transaction. Transactions are only supported within a single entity group.
-- Kyle Mulka Co-Founder, DealSavant http://www.dealsavant.com On Jul 10, 8:36 pm, bejayoharen <[email protected]> wrote: > Thank you, this is helpful, especially the links. > > I am using JPA and it's not clear to me what constitutes a "get" -- > does calling EntityManager.find() always constitute a "get" or only > when the @Id of my class is the same as the underlying datastore key? > > Furthermore, the docs cited by Kyle indicate that a transaction will > always return the most recently written data. However, that > contradicts this > > http://code.google.com/appengine/docs/java/datastore/queries.html > > which says, "With the High Replication Datastore, non-ancestor queries > are always eventually consistent." > > Which is it, are non-ancestor queries are always eventually > consistent, or can transactions cause them to be strongly consistent? > > bjorn -- 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.
