If I understand correctly, GAE doesn't even use auto-increment integer fields for id's, so it may not be practical to keep the current id's anyway. Can't you export/import both the auth_user and the membership table together, so even though it will change the auth_user id's, it will also change those id's in the membership table reference field?
On Monday, January 16, 2012 12:37:55 PM UTC-5, thstart wrote: > > It is a complex case. I am using GAE and already having users. Needed to > change the database > structure, so I need to move to new GAE app. The simplest option is to > re-invite the users but they are 100s. They will need to re-register again > using email/password. Probably not big deal for them but I try to eliminate > this step - if it is possible to migrate their accounts, then re-direct the > domain to the new GAE app and when they access the new site, which will > look the same they just have to login. But the ID's are used in the > database for their membership. If their ID's are different it will not > work. I am using the native GAE models for speed. web2py - only the auth > functionality plus the generated ID's. > > > > >
