On point #1, there is a way in JdO to say which attributes forms a relation or forms a join between two entities. It need not be the primarykey always.
Also I don't think having more than 1 @ManyToOne relation should be a problem. I might need to look at my app code in the evening to see how did I solve the problem. Thanks Hari http://harianantha.in On Oct 5, 2010 9:52 AM, "Dave Hicks" <dh...@i-hicks.org> wrote: Hi Hari, I don't follow what you're saying in #1 below. #2 - This is just the way I have always modeled classes using JPA. In a relational database, the @ManyToOne would cause the key of the owning entity to be stored in the row. In this case, the "Rating" table would have a column to hold the Person_Id. It's unclear to me how this works with the DataNucleus datastore in GAE. Here's an example of a similar relationship that is supposed to work in GAE: http://gae-java-persistence.blogspot.com/2009/10/creating-bidrectional-owned-one-to-many.html Obviously, the difference is that I have another @ManyToOne that references another entity type. I've always felt like I had a firm handle on JPA, but using it with GAE has been a very discouraging endeavor, so far. Thanks for the feedback, Dave On 10/04/2010 11:56 PM, Hariharan Anantharaman wrote: > > Hi, > I have encountered similar error ... -- You received this message because you are subscribed to the Google Groups "Google App Engine fo... -- 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 to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
