My question was unclearly formulated. I intended to ask, would it be possible to do what I described *after* the migration? In other words, would calling db.Key() on the str(old_key) 'convert' it to the new key? My plan is to do a simple brute-force copy, then convert keys on-demand in a lazy fashion after migration.
I previously saw a 'rebuild key' script: http://blog.shnap.com/migrating-to-the-google-app-engine-high-repl I assume this can be called 'after migration'. But my question is based on (wishful?) thinking that perhaps, simply calling db.Key on a legacy MS string key would be recognized and converted to the appropriate format for the aliased MS datastore. I also understand that I can do a schema change before the migration. And do appreciate Robert's suggestion to make a virtue out of necessity during the conversion. But my philosophy is to keep things simple and not try to do too much at one time:) But On Aug 4, 6:24 pm, Tim Hoffman <[email protected]> wrote: > Hi John > > You examples are the same > > old_keys = [str(key1), str(key2),str(key3)] > new_keys = [str(db.Key(i)) for i in old_keys] > > new_keys would be > > new_keys = [db.Key(i) for i in old_keys] > assuming new_keys has been declared as db.ListProperty(db.Key) > > Rgds > > Tim -- 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.
