I would suggest to play with low level API before you make decision between JDO/JPA/Objectify/twig
That will help you better understand bigtable. On Jan 5, 1:29 pm, Didier Durand <durand.did...@gmail.com> wrote: > Hi, > > I am also a big fan of Objectify: simple to understand, efficient, > light-weight, open source. (+ very well documented!). I abandonned > JDO / JPA for it. > > Before starting with jdo / jpa, you should read this thread (posts by > Ikai Lan from Google especially): future of JDO / JPA on GAE doesn't > look so bright. > Readhttp://groups.google.com/group/google-appengine-java/browse_thread/th... > > good luck > regards > > didier > > On Jan 4, 8:16 pm, John <jwb...@gmail.com> wrote: > > > > > > > > > If your app is only for GAE (it will not need to run in a 'standard' Java > > Web App container) Objectify > > <http://code.google.com/p/objectify-appengine/>provides annotation-based > > persistence with a very thin layer over the GAE > > datastore. There are certainly limitations with JPA/JDO. My preference is > > JDO for portable code, as it is more consistent with a non-SQL database. > > Among the more annoying limitations in JDO is the prohibition of > > superclass-table inheritance. -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
