Note that fetching and re-storing has to update some subtle issues if you're deleting properties.
See http://groups.google.com/group/google-appengine/browse_thread/thread/5a00e44cc56ae0d6/08f6b0ab02ce6f10#08f6b0ab02ce6f10 and http://code.google.com/p/googleappengine/issues/detail?id=2251 . On Oct 20, 6:40 am, "Nick Johnson (Google)" <[email protected]> wrote: > Hi, > Changing the model definition will not update entities already written to > the datastore. If you need the existing entities indexed on this field, you > will need to iterate through them all, fetching and re-storing them. > > -Nick Johnson > > > > > > On Mon, Oct 19, 2009 at 9:48 PM, tamakun <[email protected]> wrote: > > > Can anyone tell me if they've run into a similar problem to the > > following? > > > I had an entity with a TextProperty originally, i wanted to add a > > StringProperty so I updated the model and added new indexes for > > querying based on the new StringProperty. > > > It seems that assigning a StringProperty property with a TextProperty > > property will change the type of that property to db.Text so that it > > doesn't show up in queries/filters because those aren't indexable, but > > there doesn't seem to be a way to change it back. I've tried > > assigning None and doing put() on these entities but getting the same > > result (don't show up in queries that filter based on the new > > StringProperty). > > -- > Nick Johnson, Developer Programs Engineer, App Engine > Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: > 368047- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
