On Apr 16, 12:08 pm, ryan <[email protected]> wrote:
> in both cases, a successful put() on the entity in question will fix
> the problem. we're still working on issue 901, and we definitely
> expect to have that resolved soon. as for put() and delete() calls
> that return errors (like timeouts), we're always working to reduce
> those, but they'll unfortunately always be possible, so you'll want to
> plan for that.
Are you saying that if a put fails due to a timeout (and there appear
to be multiple different sorts of timeouts that happen in practice),
that the put operation can be half complete? If so, then does google
have recommended code for handling timeout exceptions during puts that
leave the datastore in a defined state? For example, after a failed
put, should I try a delete if a key is available?
I'm sure that many people would want to know what the best approach
is.....
Thanks
Philip
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
