Yep. The example is documented here: http://googleappengine.blogspot.com/2010/03/read-consistency-deadlines-more-control.html
<http://googleappengine.blogspot.com/2010/03/read-consistency-deadlines-more-control.html>Query q = pm.newQuery(Employee.class); q.addExtension("datanucleus.appengine.datastoreReadConsistency", "EVENTUAL"); On Fri, Mar 26, 2010 at 5:12 PM, Isdal <[email protected]> wrote: > Hi all, > > Thanks for all new new features in 1.3.2! > > I was just wondering if it is possible to use the > "ReadPolicy.Consistency.EVENTUAL" feature and still use the JDO > interface. > > I am currently getting a PersistenceManager with: > JDOHelper.getPersistenceManagerFactory("transactions- > optional"); > > Is there a way to tell the PersistenceManager to tell the datastore to > accept eventually consistent reads? Most of my app can handle stale > data, and any performance improvement would be great! > > Thanks! > > // Tomas > > -- > 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]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- Ikai Lan Developer Programs Engineer, Google App Engine http://googleappengine.blogspot.com | http://twitter.com/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 [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=en.
