Hi Uri, Glad you found your issue. I'm currently trying to convert my application too, so I've had similar headaches.
In a few cases where I've used string encoded keys, I've been updating/ creating new entities to use key_name or id instead of string encoded key. Then you can use get_by_key_name or get_by_id or key_from_path methods to get the keys (and this will work on hrd and ms versions). I think auto-generated ids are unique per entity group. Have you been using ReferenceProperties to handle the relationships? If so, I think those will be updated correctly (i.e. they'll use the newly created object). With the many-to-1 relationships, did you use lists of string encoded keys? I think you can just use db.Key instead and those may be updated automatically (not sure about this one though). Good Luck, Rob On Jul 4, 10:08 am, Uri Lukach <[email protected]> wrote: > Hey Bert, > > It appears that you are correct. > > The *datastore_admin **did not** * preserved entity keys, and part of my > entities have encoded keys to other entities for 1-1 or 1-Many references. > > It seems that after the copying process the encoded keys have the *same > ending* . So I mistakenly thought they were the same. > > Is there away to preserve the entity keys? > > I am using encoded keys to maintain references in a lot of places... > > Thanks, > Uri -- 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.
