[appengine-java] Re: Can't decide: JDO, Twig-Persist or Objectify?

2010-05-03 Thread Nacho Coloma
I just felt that I wanted to manage the references (keys) myself, so I could have more control over when and how those references are instantiated - Twig seems to do that for you (great in many ways), but I have some situations with my application where I think that could have a performance

Re: [appengine-java] Re: Can't decide: JDO, Twig-Persist or Objectify?

2010-04-27 Thread Jeff Schnitzer
The advantage of Objectify's key management is the generified Key? class, which helps keep your code straight. Jeff On Mon, Apr 26, 2010 at 5:16 AM, Christian Goudreau goudreau.christ...@gmail.com wrote: I didn't try, but I'm sure that if you set a Key field that doesn't exist in the

[appengine-java] Re: Can't decide: JDO, Twig-Persist or Objectify?

2010-04-27 Thread jbdhl
For your information I ended up choosing Objectify. I picked that because... * of its very informative, yet short and elegant, documentation. In fact, it is a far more precise and explanatory description of datastore than in Google's own GAE documentation; * the simple, yet powerful API. I

[appengine-java] Re: Can't decide: JDO, Twig-Persist or Objectify?

2010-04-26 Thread David Sowerby
Hi Christian That's interesting ... I just felt that I wanted to manage the references (keys) myself, so I could have more control over when and how those references are instantiated - Twig seems to do that for you (great in many ways), but I have some situations with my application where I

Re: [appengine-java] Re: Can't decide: JDO, Twig-Persist or Objectify?

2010-04-26 Thread Christian Goudreau
I didn't try, but I'm sure that if you set a Key field that doesn't exist in the datastore, it will be stored with the key you wanted. If I recall, store only auto assign a key when the key field is null or doesn't exist. @Key private long id; Christian On Mon, Apr 26, 2010 at 7:59 AM, David

[appengine-java] Re: Can't decide: JDO, Twig-Persist or Objectify?

2010-04-26 Thread Andreas Borglin
Hi. The Objectify/Twig/SimpleDS authors participated in an interview at http://borglin.net/gwt-project/?page_id=604 Might help you further in making a decision. On Apr 24, 9:04 pm, jbdhl jbirksd...@gmail.com wrote: Hi I really can't decide which datastore abstraction to use for my app. Any

[appengine-java] Re: Can't decide: JDO, Twig-Persist or Objectify?

2010-04-25 Thread David Sowerby
hi jbdhl I wish there was an easy answer too - but I suppose at least we have choice! My experience, which I hope will at least help you a bit For back ground I am transferring a prototype developed using a db4o back end, but had little done for the UI. There are a lot of

Re: [appengine-java] Re: Can't decide: JDO, Twig-Persist or Objectify?

2010-04-25 Thread Christian Goudreau
I have one question in mind after reading what you wrote, in wich way you have better control in Objectify than Twig ? I'm interested since I moved from Objectify to Twig and didn't end up in that situation, yet. For the cons of only one Developper, he may be alone, but he answer every single one

[appengine-java] Re: Can't decide: JDO, Twig-Persist or Objectify?

2010-04-24 Thread bufferings
Hi I like Slim3. http://sites.google.com/site/slim3appengine/ -- 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