Errors used in the Python datastore API.
- exception google.appengine.api.datastore_errors.CommittedButStillApplyingsource
The write or transaction was committed, but some entities or index rows may not have been fully updated. Those updates should automatically be applied soon. You can roll them forward immediately by reading one of the entities inside a transaction.
- exception google.appengine.api.datastore_errors.Errorsource
Base datastore error type.
- exception google.appengine.api.datastore_errors.NeedIndexError(error, original_message=None, header=None, yaml_index=None, xml_index=None)source
No matching index was found for a query that requires an index. Check the Indexes page in the Admin Console and your index.yaml file.
- exception google.appengine.api.datastore_errors.Rollbacksource
May be raised by transaction functions when they want to roll back instead of committing. Note that any exception raised by a transaction function will cause a rollback. This is purely for convenience. See datastore.RunInTransaction for details.
- exception google.appengine.api.datastore_errors.Timeoutsource
The datastore operation timed out, or the data was temporarily unavailable. This can happen when you attempt to put, get, or delete too many entities or an entity with too many properties, or if the datastore is overloaded or having trouble.