[google-appengine] Re: BadValueError: Property fAmount must be a str or unicode instance, not a float
Thank you Alex. That took care of the issue. On Mon, Feb 2, 2009 at 8:35 PM, Alexander Kojevnikov alexan...@kojevnikov.com wrote: On Feb 3, 11:11 am, Mark mark.hac...@gmail.com wrote: My app is working fine locally on dev_appserver, but I am getting the error in the subject line after I do an appcfg update. The error occurs on a query that happens on the welcome page of the app. I think I uploaded a version that had FloatProperty in one of my databases, but I can't remember my exact order of operations that led to this error. Now, I've changed my application locally so that that field in my database is a StringProperty (I'll deal with the floatness of it later) and I get an error after I do appcfg update. You probably still have entities in the datastore with float property values. If you have few of them, go to the Data Viewer and edit the values manually. There is an option to change the type of the property values. If you have a lot of them, you will need to write a data migration script, see this article for some pointers: http://code.google.com/appengine/articles/update_schema.html I also tried using Python 3.0 (I got an error message from the appserver that said I can't use FloatProperty with 2.5), but I got an error in dev_appserver.py because execfile() is obsolete (is there a workaround for this, yet?) Python 3.0 is not supported by the App Engine, you need to use Python 2.5. Star this issue if Python 3.0 support is important for you: http://code.google.com/p/googleappengine/issues/detail?id=909 --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[google-appengine] Re: BadValueError: Property fAmount must be a str or unicode instance, not a float
On Feb 3, 11:11 am, Mark mark.hac...@gmail.com wrote: My app is working fine locally on dev_appserver, but I am getting the error in the subject line after I do an appcfg update. The error occurs on a query that happens on the welcome page of the app. I think I uploaded a version that had FloatProperty in one of my databases, but I can't remember my exact order of operations that led to this error. Now, I've changed my application locally so that that field in my database is a StringProperty (I'll deal with the floatness of it later) and I get an error after I do appcfg update. You probably still have entities in the datastore with float property values. If you have few of them, go to the Data Viewer and edit the values manually. There is an option to change the type of the property values. If you have a lot of them, you will need to write a data migration script, see this article for some pointers: http://code.google.com/appengine/articles/update_schema.html I also tried using Python 3.0 (I got an error message from the appserver that said I can't use FloatProperty with 2.5), but I got an error in dev_appserver.py because execfile() is obsolete (is there a workaround for this, yet?) Python 3.0 is not supported by the App Engine, you need to use Python 2.5. Star this issue if Python 3.0 support is important for you: http://code.google.com/p/googleappengine/issues/detail?id=909 --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
