since hrd is eventually consistent, you need to restructure your app to not immediately query the newly commited data after a transaction.
welcome to nosql my app builds its own result page that assumes the committed data is there. by the time the user refreshes the page the data is there and queryable as normal On Feb 18, 9:27 pm, sj <songj...@gmail.com> wrote: > I'm using HRD because I want make changes to multiple entities within a > single transaction using entity groups. > > Understand that Non transactional (non ancestor) queries may see all, some, > or none of the results of a previously committed transaction. > > The problem I facing now is: > > - After commit an transaction for adding new record to db > > Transaction tx = pm.currentTransaction(); > tx.begin(); > pm.makePersistent(object); > tx.commit(); > > - > > Follow by query the record committed, sometime it will return result and > some time just return as null > > Query q = pm.newQuery(queryStatement); > CompanyProfile result = (CompanyProfile) q.execute(); > > p/s: When turn off HRD, it work perfectly. > > Any workaround? > > Thanks > > Rgds SJ -- 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-java@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.
