[google-appengine] Re: can I remodel an already exist model field from Date to long without any problem?
>From my experiences on developing apps on gae, I think it is best never using Date type. Just use long type instead. On Mar 20, 3:47 am, Kaan Soral wrote: > If I were you I would write an on-use converter, there will be no > errors and you don't have to confuse yourself with mapreduce > Just check the model's property when you need it and write the new > version if it's the old one > > On Mar 19, 4:57 am, Robert Kluin wrote: > > > If you have existing data you'll need to migrate it. There are a > > couple techniques you can use, depending on your language choice (Java > > or Python). Basically they will all involve iterating over your > > entities, converting the property, then reputing the entity. If > > you've got a lot of data you might look at using the map-reduce lib. > > >http://code.google.com/appengine/articles/update_schema.htmlhttp://co... > > > Robert > > > On Fri, Mar 18, 2011 at 18:31, Tapir wrote: > > > . > > > > -- > > > 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 > > > athttp://groups.google.com/group/google-appengine?hl=en. -- 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: can I remodel an already exist model field from Date to long without any problem?
If I were you I would write an on-use converter, there will be no errors and you don't have to confuse yourself with mapreduce Just check the model's property when you need it and write the new version if it's the old one On Mar 19, 4:57 am, Robert Kluin wrote: > If you have existing data you'll need to migrate it. There are a > couple techniques you can use, depending on your language choice (Java > or Python). Basically they will all involve iterating over your > entities, converting the property, then reputing the entity. If > you've got a lot of data you might look at using the map-reduce lib. > > http://code.google.com/appengine/articles/update_schema.htmlhttp://code.google.com/p/appengine-mapreduce/ > > Robert > > On Fri, Mar 18, 2011 at 18:31, Tapir wrote: > > . > > > -- > > 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 > > athttp://groups.google.com/group/google-appengine?hl=en. -- 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.
