[google-appengine] Confusions on transactions and concurrent writes to entity groups

2008-09-18 Thread DXD
I appreciate any clarifications on my situation as follows. I have an entity group whose the root entity is called "root". When a particular URL is requested, a new entity is added to this group as a direct child of root. The code looks similar to this: def insert(): root = Root.get_by_key_name

[google-appengine] Re: Confusions on transactions and concurrent writes to entity groups

2008-09-23 Thread DXD
ion times out (due to too much contention or some other > > issue) the other parts of the transaction will not be applied. For > > more details > > see:http://code.google.com/appengine/docs/datastore/transactions.html#Usi... > > > Happy coding, > > > Jeff > >

[google-appengine] Problem creating new application!!!

2008-10-09 Thread DXD
I got a problem creating a new application. The app identifier was confirmed to be available; the app title was set to be the same as the identifier. The authentication option was set to the default. But when I hit "Save", it always said "Server Error A server error has occurred" And the app was

[google-appengine] Re: Problem creating new application!!!

2008-10-09 Thread DXD
; Hi, > > > This is an issue with the Admin Console, and we hope to have it fixed > > shortly. > > > -Marzia > > > On Thu, Oct 9, 2008 at 4:04 PM, Marzia Niccolai <[EMAIL PROTECTED]> wrote: > > >> Hi David, > > >> What is the app id you we

[google-appengine] Concurrency Control in the datastore

2008-11-06 Thread DXD
Hi, I'm a new GAE developer, and now particularly interested in investigating the difference in concurrency control between the datastore and a traditional RDBMS. I looked at Ryan Barrett's presentation about the datastore in the Google IO sessions (http:// sites.google.com/site/io/under-the-cove

[google-appengine] Re: Concurrency Control in the datastore

2008-11-12 Thread DXD
Thanks Alexander. So now this is my guess about the rules of the datastore's timestamp- based scheduler. If someone could, pls correct where I'm wrong in here (basically I consolidated the theoretical timestamp-based scheduler with what I understand from Ryan's presentation): Each transaction T

[google-appengine] Re: Concurrency Control in the datastore

2008-12-03 Thread DXD
Hi Ryan, So actually you guys use the multiversion timestamp control, and the rules of the scheduler are in fact more straightforward than what I outlined. I believe they are as follows (pls correct me if I'm wrong somewhere): When a transaction T starts, it is assigned a timestamp TS(T) generat

[google-appengine] Re: Concurrency Control in the datastore

2008-12-11 Thread DXD
Wonderful! Great design!!! Thanks Ryan. David. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from thi

[google-appengine] Re: Concurrency Control in the datastore

2008-12-18 Thread DXD
Ryan, I have an additional little question about the read action and rollback. Suppose we have a group whose root is R with 2 entities X and Y. Now tx T1 updates X and successfully commits. So CTS(R) becomes TS(T1), but Y doesn't have an entry for TS(T1) (because it didn't get updated by T1). Th