Having re-read your original question, I see now that my answer doesn't apply at all :P
To do this with appcfg.py download_data, I'd see what you can do with the exporter class that you're defining for each model that you're downloading. You could add a timestamp field as I suggested, and define a function in your exporter class that tests that this field exists and/or is within a particular range. From there, you could either set a boolean value and use it to pare down your result set in post-processing, or raise an exception. You're probably not going to avoid having to download every entity (without patching download_data.py) as the functionality you're looking for doesn't appear to exist. Hope that's more helpful. On Jun 22, 2:19 pm, Jonathan Feinberg <[email protected]> wrote: > On Jun 22, 2:18 pm, Tony <[email protected]> wrote: > > > If you add a property such as: created_at = db.DateTimeProperty > > (auto_now_add=True) to the models you are moving, you could then query > > on that property to find entities created during any timeframe. > > That's true. What does that have to do with appcfg.py download_data? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
