You might want to take a look at CommittedButStillApplyingException On Tue, Dec 21, 2010 at 1:08 PM, ss.require <ss.requ...@gmail.com> wrote:
> Please, help! > According to this: > http://code.google.com/intl/uk-UA/appengine/articles/life_of_write.html. > > Let's suppose that I call the low-level put method outside of a > transaction and an exception throws. If exception occures at the > commit phase entity won't be saved otherwise if exception occures at > the applyed phase entity will be saved. > > Is there a way to find out entity is really saved or not in the > datastore after exception? > > If I execute the same operation inside a transaction, for exampe: > Transaction tx = datastore.beginTransaction(); > try { > .... put entity code ... > tx.commit(); > } finally { > if (tx.isActive()) { > tx.rollback(); > } > Suppose exception occures in the apply phase, then tx.rollback() will > be fired? Can it make sure that enitty really won't be saved in the > datastore? > > -- > 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<google-appengine-java%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- 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.
