If you are using auto generated keys or keys generated using the allocateIds() method, no, this should never happen. In fact, any key created using allocateId will never appear again even if you never save an entity with that key.
One thing to note is that that IDs are not monotonically incrementing (ID 1, 2, 3, 4, 5 ... etc) - this is very hard to do in a scalable fashion. IDs more or less are increasing, but we cannot guarantee that the ID of an entity will be greater than an entity saved before it (you might concurrently allocate two batches of IDs, for instance). -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Thu, Dec 15, 2011 at 8:59 AM, Juna <[email protected]> wrote: > Hi, I have been looking info about this and I haven't find an exact answer > (or I haven't known read the answer). > > I am imagining a paranoic scenario where I delete an entity of certain > kind and at some point in the future I create another entity of the same > kind which receives the same key value. > In this case my app relies in the datastore to generate the keys, I am not > generating my own keys. > > I supose that an asteroid will hit my house before this issue happens, but > I am curious. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine-java/-/FFDSjzwq3-IJ. > 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-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
