Hi Dexter, Lack of global transactions is not a bug, but rather a consequence of having a distributed datastore. While it's possible to introduce them, it imposes a large additional overhead, which most users don't want.
For details on one way to implement extended transactions on App Engine, see my blog post here: http://blog.notdot.net/2009/9/Distributed-Transactions-on-App-Engine -Nick Johnson On Sun, Apr 4, 2010 at 4:17 PM, Dexter <[email protected]> wrote: > The global conservation law is a show stopper for many banking type > application in Google Apps. > Check http://code.google.com/p/googleappengine/issues/detail?id=313 > for details. > > It seems that google is not going to bring 2 row concurrency anytime > soon. However if a large number of people are interested it might get > a higher priority. > > Can someone please let me know how do we let google know how many ppl > need this. Continue riting on this ... is there already a provision > for wishlist ranking etc ? > > Thanks > PK > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. 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.
