While I had a similar problem at one point, the eventual cause was not passing the correct timestamps to default= in model fields, which may cause the timestamps to appear skewed while in fact they indicate the instance spin-up timestamp. so if you have anywhere default=datetime.utcnow() you should use: default=lambda:datetime.utcnow()
Hope I helped (and that skews of more than a minute or even 10 seconds, don't exist) On Mar 3, 3:54 pm, Ng Ka Ka Eric <ngk...@gmail.com> wrote: > Hi Raymond, > > Just watched the video. Thx for pointing this reference. > > I really didnt expect that the machines are not time synced (can be off for > 40mins?!) are there any technical difficulties to sync them? And in this > case, for whatever reason if we want to record the time when the request is > made into DS, how can we do that? > > - eric > > Sent from my iPhone > > On 2011年3月3日, at 下午6:20, "Raymond C." <windz...@gmail.com> wrote: > > > > > > > > > According to Brett's data pipelines' talk > > (http://www.youtube.com/watch?v=zSDC_TU7rtc, around 35:50), its not > > -- > > 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 > > google-appengine+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/google-appengine?hl=en. -- 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 google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
