Ah, it is the parentKey property again. Seems like I don't have another choice. Anyways, given the key is supposed to contain whole ancestor chain, this seems weird.
2010/5/6 Jaroslav Záruba <[email protected]> > I mean "it can't be done" without another property. > Currently I'm looking at the last code example in Uses For > transactions<http://code.google.com/appengine/docs/java/datastore/transactions.html#Uses_For_Transactions> > ... > > On Thu, May 6, 2010 at 9:40 PM, timwhunt <[email protected]> wrote: > >> Hi Jaroslav, >> >> I didn't take it as "it can't be done", but I haven't tried to >> implement it, and this stuff is new to me. The suggestions included a >> parent property in the child object, which seems fairly >> straightforward. However, I was expecting/looking for methods that >> worked on the inherent properties of keys. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<google-appengine%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/google-appengine?hl=en. >> >> > -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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?hl=en.
