I have a clarification question. Does this time skew also apply to the datastore? In particular, if I have an entity with a DatetimeProperty using the "auto_now" feature, will the times in my property be potentially skewed? My guess is that since the datastore is so distributed, the same kind of skew is possible. This might be a good thing to mention in the docs for DateTimeProperty, because so many of us are probably used to trusting the database as a centralized place to get a timestamp.
-peter On Oct 24, 8:15 pm, ryan <[EMAIL PROTECTED]> wrote: > sorry, but we're unlikely to ever provide an upper bound on clock sync > across servers. jon's right that it will generally be in the > neighborhood of seconds, but providing a guarantee would be similar to > attempting global synchronization across a distributed system. you > should generally try to avoid depending on global counters at all, but > if you need one, you can use either datastore Key ordering or > datastore transactions, depending on your needs. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
