imho, the low level api is quite simple and straightforward. The relevant docs for Python is useful to me.
there is nothing wrong with JPA/JDO. DAO + Low Level API implementation without an additional JDO layer works for me. On Thu, Sep 24, 2009 at 5:23 AM, Marcel Overdijk <[email protected]>wrote: > > I think the docs about low level api is rather limited. Some examples > would be nice. > > On Sep 23, 4:33 pm, Clay Lenhart <[email protected]> wrote: > > +1 > > > > We're having a similar discussion here: > > > > http://groups.google.com/group/google-appengine-java/browse_thread/th... > > > > Andy, > > My view is that there is no productivity difference between the two. > > > > It might be good to show us what is difficult to do in the datastore > > but easy in JDO. > > > > Cheers, > > Clay > > > > On Sep 23, 11:02 am, datanucleus <[email protected]> wrote: > > > > > > > > > > BigTable simply is not a relational db, so it is highly misleading to > > > > fake a relational wrapper and to me it caused lots of pain. > > > > > Apart from the fact that JDO is not a "relational wrapper". The API > > > and metadata are object-based; only a subset of metadata is specific > > > to "mapped" datastores and this is marked clearly in the (DataNucleus) > > > docs. > > > > > As ever, if you have some specific issue to raise why not define it - > > > e.g something that can be done in the low level API that can't be done > > > via a generic API. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en -~----------~----~----~----~------~----~------~--~---
