I think you might be a little confused about the difference between
appengine's
transaction in a distributed environment and an enterprise 2-phase
transaction
in a more classic client server architecture?
appengine uses a distributed datastore, so entities are stored all
over the place by default.
Huh?
As you are only able to do work in a single transactional unit-of-work
on a single entity-group, rollback must be considered "usefull".
In the above mentioned snippet, an Account entity is looked-up,
updated and a child entity TransactionRecord is added, all in a single
entity-group, namely t
Hi,
entity group is not useful at rollback but rather limits you to which
updates you can do: all the entities you touch in a single transaction
must be in the same entity group.
So, designing your groups properly is a key design issue in GAE to
avoid unnecessary complexity when you later need to
I didn't look at your snippet in detail, but you need transactions,
and that means the entities
need to be in the same entity group, that is have same ancestor.
On May 31, 2:53 am, pavb wrote:
> Hi,
>
> Yes all the datastore insert, update, delete done in the transaction
> are canceled by the rol
Hi,
Yes all the datastore insert, update, delete done in the transaction
are canceled by the rollback operation.
The put of your updated Account is validated only if the transaction
commit is done succesfully.
PA
On 30 mai, 07:57, Jacob wrote:
> I am writing some code that needs to do a rollba
