Hey Guys, I am a big fan of App Engine, but seem to be stuck on a problem: Is there any option for storing relationships such that entity keys are not dependent on GAE?
The background: We are building a web app that we believe our customers would like to have a core component on their internal networks. Since we would like to use Google App Engine on our side (for the rest of the users), I am trying to find the best way for storing relationships that allows the core data model to not be stuck to only run on the App Engine platform. When doing this the challenge seems to be finding the best way to model relationships. I played with JDO, but since JPA implementations seem to be more easily available - it seems to be the best option. The big challenge is in supporting relationships. The documentation seems to indicate that this is not possible, which given that JPA exists for increased portability seems surprising to me. From http://code.google.com/intl/pl/appengine/docs/java/datastore/relationships.html : "The child class must have a key field whose type can contain the parent key information: either a Key, or a Key value encoded as a string." Will appreciate guidance. Vineet --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
