http://code.google.com/appengine/articles/transaction_isolation.html
On Nov 7, 11:38 am, DXD <[EMAIL PROTECTED]> wrote: > 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-covers-of-the-google-app-engine- > datastore), and got some brief understanding of it. To me, doesn't > look like Google implemented the Timestamp-based scheduling method > (although there does exist a timestamp attached with each row). The > method I'm talking about is the "traditional" timestamp method > mentioned in section 9.8.1 of the book "Database System > Implementation" (http://infolab.stanford.edu/~ullman/dbsi.html) where > each row should have the "read time" and the "write time", and based > on the comparison between these values and the timestamp of the > transaction, the scheduler will decide how to handle the read/write > request from the transaction. Is my statement true? If so, could > anyone pls point me to some (as detailed as possible) references/ > papers/technical documentations/presentations about how/what method > Google actually used to implement concurrency control? (did they > follow some standard method or invent their own?). I need this asap, > so greatly appreciate if someone could give me some help. > > Thanks, > 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 this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
