Hi David,
Even if a put request to the datastore is not run in a transaction,
the operation is automatically retried. Contention is not unique to
transactions. The benefit of using transactions, is that if one write
in the transaction times out (due to too much contention or some other
issue) the
To further clarify. All writes are transactional. Details on how the
transactions work can be found in ryan's presentation from Google I/O:
http://snarfed.org/space/datastore_talk.html The section on
transactions specifically begins at slide 49. You can also watch the
video here:
http://sites.goo
Thanks Jeff. Things are clear now.
Cheers,
David.
On Sep 22, 1:52 pm, Jeff S <[EMAIL PROTECTED]> wrote:
> To further clarify. All writes are transactional. Details on how the
> transactions work can be found in ryan's presentation from Google
> I/O:http://snarfed.org/space/datastore_talk.htmlTh
"All writes are transactional."
Does this mean updating values on a single entity will lock the entire
group when put() is called?
On Sep 22, 10:52 am, Jeff S <[EMAIL PROTECTED]> wrote:
> To further clarify. All writes are transactional. Details on how the
> transactions work can be found in r
On Fri, Oct 31, 2008 at 5:37 PM, jeremy <[EMAIL PROTECTED]> wrote:
> "All writes are transactional."
>
> Does this mean updating values on a single entity will lock the entire
> group when put() is called?
Yes.
Dave.
--~--~-~--~~~---~--~~
You received this mess
It is not really a lock. The first finished put will win, the other
concurrent puts will fail and retry.
On Oct 31, 8:37 pm, jeremy <[EMAIL PROTECTED]> wrote:
> "All writes are transactional."
>
> Does this mean updating values on a single entity will lock the entire
> group when put() is called?
