But not python. It seems to cause the javascript front ends the most woe. T
On Saturday, May 25, 2013 8:26:06 AM UTC+8, Ray wrote: > > In short: if any part of your applications use 32 bit integers (which is > still the default for many environments) to store any IDs of entities, your > application will break once this change is deployed. > > > On Saturday, May 25, 2013 8:04:08 AM UTC+8, Chris Ramsdale wrote: >> >> Hello App Engine folks, >> >> In the upcoming 1.8.1 release, the Datastore default auto ID policy in >> production will switch to scattered IDs to improve performance. This >> change will take effect for all versions of your app uploaded with the >> 1.8.1 SDK. >> >> You can preview the new behavior in the dev server, where scattered auto >> IDs are the default. These IDs are large, well-distributed integers, but >> are guaranteed to be small enough to be completely represented as 64-bit >> floats. If you still need legacy ids for some entities (e.g. because you >> want smaller numbers for user-facing ids), we recommend you use the >> allocateIds() API, which will continue to behave as before. You can also >> override the default auto id policy by setting the new auto_id_policy option >> in your app.yaml/appengine-web.xml to legacy, but please note that this >> option will be deprecated in a future release and will eventually be >> removed. >> >> If you have any questions don't hesitate to follow-up here or drop me a >> line directly. >> >> -- Chris >> >> Product Manager, Google App Engine >> > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
