hi alex! serializing the list property into json shouldn't make much of a difference in the timeout rate, but you're welcome to try it. honestly, though, .01% is noticeable, but i wouldn't exactly call it "large." regardless of how your data is shaped, you'll at least see a small timeout rate. .01% is in the ballpark.
as for deleting a property in your model definition, that's backward compatible. the existing data in the datastore will remain unchanged. when you load entities with the new model definition, they'll just ignore the old property, and not populate it in new entities. other changes, e.g. changing a property type or adding a required property, will cause exceptions when you fetch entities created with the old model definition. you can use Expando and optional properties to help with schema changes like these. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
