Hi, If you look at the recent recommandations of Google, the 1st best practice is probably to move away from JDO and go to either low-level API or some 3rd party package like Objectify (my choice) to give you good long-term perspectives.
regards didier On Jun 24, 9:47 am, Martin Newstead <[email protected]> wrote: > I would like some help and advice on how to model my entities using > JDO on GAE. My problem is this, I have a bunch of Users and each User > may create zero or more Tracks. Users may exist without a Track but > Tracks may not exist without a User who created them. Other attributes > on the User and the Track may updated. I would like to be able to > query the Tracks and retrieve some attributes from the User who > created the Track. The attributes from the User may get updated. In > SQL this would be > > select u.displayName, t.trackName from User u, Track t, where > t.userId=u.userId > > I have some ideas and have tried various things but this isn't a post > on why doesn't something work, more of what is the best practice to > solve this problem. > > thanks <M -- 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.
