But, be mindful of the possibility of using the new remote_api to create such updated counters, rather than "cron", if it's a one-time change.
With a few extra lines of Python and a machine with enough time to run the updates, out-of-date data structures can be brought up to date without having to perform the hijinks of incremental updates on the live site. For instance, with my deepFetch routine (see the Cookbook entry here: http://is.gd/kChr), it's just matter of writing the usual "for x in deepFetch(queryFun):" routine to iterate through and update all data structures. -Bryan On Feb 23, 7:54 pm, "Sebastian E. Ovide" <sebastianov...@gmail.com> wrote: > That's right. That is the only way... so you need to design the application > with counters in mind. > > If you need to add a counter that you have not planned, then you need to > create a "cron like" task that counts those records and store the > information in your new counters shards. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
