On May 2, 2:40 pm, jtuchscherer <[email protected]> wrote: > John, are you saying that Twig, Objectify, SimpleDS, Slim3 and Siena > don't have this problem?
I can only definitivly speak for Twig but I am certain that the others also would not suffer this problem or many many of the other issues with JDO-GAE. > If yes, which one can you recommend? Well as founder of Twig I would of course recommend it! :) However, the other projects all have strengths which you might want to look into. Comparing Twig with the other non-standard datastore interfaces I would say it has a slightly higher level of abstraction which has the advantage of making your code simple at the cost of being less aware of when each peice of data is loaded. > I am a > little bit reluctant to use anything that makes your code tied to GAE. > The beauty of JDO/JPA is that I can use the same code and deploy > anywhere else. I think you will find that this is not an easily achievable goal. > But if that is my only option to get around this > limitation I probably would use Twig, Objectify ... You will certainly save yourself a LOT of time and grey hairs. -- 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.
