The documentation I wrote up here might help: http://code.google.com/p/objectify-appengine/wiki/Concepts
You might consider using something like Objectify (or Twig, or SimpleDS, etc) instead of the Low-Level API. Jeff On Wed, Feb 17, 2010 at 9:23 PM, Patrick Twohig <[email protected]> wrote: > Aside from the Javadocs, does there exist any further documentation on the > GAE/J low-level API. I've had a handfull of issues with it so far and I'm > at a bit of a loss. I'm having trouble with ancestor queries. > Specifically, I'm not getting any child entities when I look for objects > with no kind specified and just an ancestor. However, the equivalent code > in python performs as expected. > > I was also curious how GAE/J organizes transactions. From what I gather in > the documentation, each transaction is organized in a ThreadLocal stack. > Every time you call DatastoreService.beginTransaction() it creates a new > transaction, pushes it on the thread local stack then when it's done, it's > popped of. I was curious if it may be possible to add a method that can > provide the current transaction given a particular key somehow. > > > -- > Patrick H. Twohig. > > Namazu Studios > P.O. Box 34161 > San Diego, CA 92163-4161 > > -- > 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. > -- 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.
