The query ultimately delegates to the low-level batch get method on com.google.appengine.api.datastore.DatastoreService. This method returns a Map. The ordering you're seeing is just the iteration order of the Map (which is a HashMap). There's an existing issue to track this: http://code.google.com/p/datanucleus-appengine/issues/detail?id=132
Please star it if this is important to you. Thanks, Max On Thu, Oct 29, 2009 at 5:48 PM, David Fuelling <[email protected]> wrote: > > I'm testing some code that mirrors the JPA batch-get example on this > page (http://gae-java-persistence.blogspot.com/2009/10/executing-batch- > gets.html<http://gae-java-persistence.blogspot.com/2009/10/executing-batch-%0Agets.html> > ). > > I start off with a list of 10 Keys (these happen to be in numerical > order starting from "Message(1) to Message(10)). When I execute the > JPA-based batch-get, I get the proper full-entities returned. > However, the List ordering is all wacky. I would expect the List > ordering of the actual full-entities to be the same as the ordering of > my key-List. > > Is that a bad assumption? The ordering appears to be consistent every > time, but it's not ordered in any discernable way. > > Thoughts? > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
