Ryan,
These 2 statements appear to contradict:
...in practice, every id-based root entity has an id
that's across all other root entities...
...bare ids or key names are generally only
interesting or useful when the rest of the path is held constant,
including the kind of the entity in
I think that this id counts for an entity-group namespace live
forever property should be documented because I suspect that many
uses of entity-groups will involve single-use names.
The only reason that I'm not running into it is that I prematurely
optimized to a single db.put, which forced me
On Dec 31 2008, 6:49 am, Andy Freeman ana...@earthlink.net wrote:
If I never allocate ids within a given entity-group namespace, does
anything for that namespace live forever (after all entities in said
group have been deleted)?
...
The total number of such groups that have entities at any
On Dec 20, 11:14 pm, Thomas Johansson prenc...@gmail.com wrote:
Is this to be interpreted as getting the following, in order, more or
less? (where the ID/Key is in square brackets)
/Image[42]
/Image[127841]
/Thread[10]/Post[42]
/Thread[10]/Post[127841]
E.g. the ID is ever increasing,
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
Can we ever experience inserting a record that will
have a lower ID than the previous?
Yes.
An application should not rely on numeric IDs being assigned in
increasing order with the order of entity creation. This is generally
the case, but not guaranteed.
from
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
Forgot to ask; How does the key fit into the hierarchy, compared to
the key_name id?
On Dec 21, 8:14 am, Thomas Johansson prenc...@gmail.com wrote:
Hi ryan,
Is this to be interpreted as getting the following, in order, more or
less? (where the ID/Key is in square brackets)
/Image[42]
Can we ever experience inserting a record that will
have a lower ID than the previous?
You can, at least that's what I'm seeing in my app. As far as I
understand, the IDs are pre-allocated in batches, and if your app
actually runs on different boxes, they will use IDs from different
batches.
