> good question. no, they're not.

> you're probably already on top of this, but just for the record, ids
> themselves aren't unique across entities. only an entity's full path
> is guaranteed to be unique. ids and key names are only guaranteed to
> be unique among entities of the same kind that have the same parent
> (or that are root entities).

That's a curious comment.  It suggests that ids may be reused if
there's another difference in the path.

However, combining that with the statement that there's no reuse for a
given path is interesting because there's no obvious place for the
datastore to keep track of what ids it has used.

Yes, one can store an indicator of what ids have been used (such as
the last id used) with an entity group, but what happens to that
indicator when the entity group goes away?  If it is destroyed and
then recreated when the entity group is recreated, how does the id
allocator avoid previously used ids?

On Dec 20, 9:13 pm, ryan <ryanb+appeng...@google.com> wrote:
> On Dec 20, 7:09 pm, jeremy <jeremy.a...@gmail.com> wrote:
>
> > are numeric ids of deleted entities reused? i really hope not.
>
> good question. no, they're not.
>
> you're probably already on top of this, but just for the record, ids
> themselves aren't unique across entities. only an entity's full path
> is guaranteed to be unique. ids and key names are only guaranteed to
> be unique among entities of the same kind that have the same parent
> (or that are root entities). more 
> inhttp://code.google.com/appengine/docs/datastore/keysandentitygroups.h...
> .
--~--~---------~--~----~------------~-------~--~----~
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-appengine@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
-~----------~----~----~----~------~----~------~--~---

Reply via email to