You should only need to call AllocateIds once for each kind. The bulkloader should do this when uploading data as of 1.3.8.
Otherwise, I think error should eventually resolve on its own--every time you get the exception, it should advance the next id pointer pretty far, so you should only see it a few times. I haven't tested this myself. --Matthew On Oct 7, 9:36 am, Hugo Visser <botte...@gmail.com> wrote: > Any suggestions? Would iterating the current entities and call the > allocate function with those keys help? I'm getting errors on migrated > data in production which is pretty bad. > > On Oct 6, 4:40 pm, Hugo Visser <botte...@gmail.com> wrote: > > > > > I've imported data from one app id to another and now I'm getting > > spurious messages of duplicate id's, apparently because the id's are > > not automatically allocated. > > > What would be the best strategy to allocate these id's again so that > > sequence generation will not attempt to use the existing id's? -- 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-appeng...@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.
