Thanks Nick and Tony for your help and clarification.  I will look in
to potential migration options in that article you sent, Tony.  Never
use int for something that might be a float! ;)

-savraj

On Jun 22, 2:00 pm, Tony <fatd...@gmail.com> wrote:
> http://code.google.com/appengine/articles/update_schema.htmldescribes
> one technique for updating your schema.
>
> On Jun 22, 12:13 pm, "Nick Johnson (Google)" <nick.john...@google.com>
> wrote:
>
> > Hi Savraj,
>
> > If you change your property from db.IntegerProperty to db.FloatProperty, all
> > your existing entities will fail to validate, and throw exceptions when
> > loaded. If you want to make this change, you need to transition all your
> > existing entities before making the update.
>
> > -Nick Johnson
>
> > On Mon, Jun 22, 2009 at 5:04 PM, Savraj <sav...@gmail.com> wrote:
>
> > > Hi App Engine-ers,
>
> > > So I've got a ton of data stored in my db -- and I've got a particular
> > > field, let's call it 'value' set as 'db.IntegerProperty()' in my model
> > > definition.  If I change this to 'db.FloatProperty()', what happens?
>
> > > I would imagine that the existing values in the db remain Integers,
> > > while the new ones coming in are floats, and that should be fine for
> > > my purposes. But will it work?  I suppose the only way to know is try,
> > > but I don't want to mangle my database, which has quite a bit of data
> > > in it.
>
> > > What will happen in this case?
>
> > > -s
>
> > --
> > Nick Johnson, App Engine Developer Programs Engineer
> > Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number:
> > 368047
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to