I use JDO but I don't use the built in relationship handling. I manage my own relationships and use JDO just for the property/entity mapping part of it. It seems to make life a lot simpler when trying to get around these types of situations. If you can make the Orders not be children of the Account class and manage your own relationships that will make your life a lot easier in the long run even if it's more work initially and your code much faster and efficient, IMHO. Also, you might want to take a look Objectify. Others here seem to like it a lot.
On Tue, May 17, 2011 at 1:38 AM, Ashley Schroder <ashley.schro...@gmail.com> wrote: > Quick update: The query interface works. I was able to run the query across > all the entities and start iterating over them (so it must lazy load when > iterating). However I could not do a size() on the collection returned, so > there must be too many items in the collection now. > > I can work around the now redundant relationship of account.getOrders() by > querying. Now to figure out the best way to add a child object without > accessing the parent's collection of children. > > Maybe I should switch to JDO+MySQL before I get in too deep - is this a > completely wrong application of GAE? > > -- > 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-java@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. > -- 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-java@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.
