I have the same problem, did you find an answer ?
On 10 oct, 21:04, Lakshmi <[EMAIL PROTECTED]> wrote:
> Hello,
>
> If we take the following example:
>
> Comment
> - post (reference to Post)
> - text
> - author
>
> where comments that are responded to become parents of other comments,
> ho
interesting question! unfortunately, right now, there's no way to
query for only root entities, ie entities that have no ancestor. i
don't know how common a use case it is, but feel free to add a feature
request on the issue tracker!
http://code.google.com/p/googleappengine/issues/list
--~--~
Sorry I completely forgot about this thread.
I added a is_root property to my model to work around this problem.
I also discovered that a root node is one that is its own ancestor.
On Oct 27, 11:02 am, "Vincent L." <[EMAIL PROTECTED]> wrote:
> I have the same problem, did you find an answer ?
> I also discovered that a root node is one that is its own ancestor.
too bad queries with ancestor('__key__') or with 'ANCESTOR is
__key__' (or the bound equivalent) don't work.
On Dec 6, 6:49 pm, Lakshmi <[EMAIL PROTECTED]> wrote:
> Sorry I completely forgot about this thread.
>
> I added a is
Yes :)
I think Entity Groups are optimized more for performance and less for
function. (Another example to reinforce this statement is the need to
pass in the parent_id in get_by_id or the underlying assertion that
the id's may not be unique outside of the entity group)
On Dec 9, 11:59 am, Andy
The characteristics of entity groups that enable performance
optimizations actually enable some fairly interesting operations.
Unfortunately, these operations are not exposed in some cases.
In this case, ancestor('__key__') should be trivial to support and not
slow things down. I don't think tha
