The routines are mentioned are all get by key_name type of operations, eventual consistency shouldn't be an issue I've also checked the "created" fields in the datastore of the "unknown replication" issue I mentioned, they were differentiating below the millisecond, it also happened just once, never happened on the sdk, happened on production once
Never really considered using Cloud SQL, I initially read about it when it first came out, it seemed like an unscalable at extreme limits / an alternative for those who use mysql and replicate the experience using appengine, I might have misinterpreted it, and I might be talking about another sql alternative that exists for appengine On Saturday, October 19, 2013 11:38:16 PM UTC+3, Nick wrote: > > Hi, I agree you need to understand and use transactions. > > Regarding your 'overwrite' scenarios, are you sure you're not just > witnessing eventual consistency and interpreting it as contention? If > something has a very low probability, yet you're seeing it a lot, maybe you > need to rethink what you think your problem is. > > If you really can't solve this or wrap your head around it, I'd recommend > trying cloudsql instead - it's something you'll be used to and understand > well. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
