I found the property for the memcache L2!!! ;) For the ordered collection I see the v2 is yet in RC* status, so I prefer to stay on the v1 version .. I noticed if I set a collection datanucleus always complains because the owner set is different from the one it expects:
Object "com.map2app.Parent@2377ff35" has a collection "com.map2app.Parent.children" yet element "com.map2app.Child@294ce5eb" has its owner set to "com.map2app.Parent@7563a320". This is inconsistent and needs correcting. org.datanucleus.exceptions.NucleusUserException: Object "com.map2app.Parent@2377ff35" has a collection "com.map2app.Parent.children" yet element "com.map2app.Child@294ce5eb" has its owner set to "com.map2app.Parent@7563a320". This is inconsistent and needs correcting. .. I solved this issue putting the owner always set to null. I know it's not an elegant solution but I am sure the workflow is right because in the unit testing I create the parent (with the children) some lines before and then I just close and re-open the pm and the transaction. No other modifications are done in the middle. Any idea? Thanks On Jan 18, 6:50 am, datanucleus <[email protected]> wrote: > > Just a last thought: in this way I have to retrieve all the children > > each time I want to order the collection .. Am I right? > > You retrieve the owner object, and it has a List. You play around with > the List to your hearts content, and the updates are saved. > > > I hope it is integrated with the second level caching system > > mechanism .. > > You can easily set the L2 cache to be memcache with a single > persistence property. -- 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.
