You're right. I confused the two: I said unowned while actually describing
inverting the relationship. Do I get half a point? ;)
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
For something large like that, I think you'll want to make your relationship
from User to LoginHistory an unowned relationship. That simply means that
LoginHistory will store an ID that points to User instead of User having a
collection of LoginHistory objects. The Google docs have more on
True. I had forgotten about the unowned relationships, but I think again I
will need to retrieve the collections in order to add the new Key, right? Of
course it's much better to retrieve a collection of keys than a collection
of entities. And maybe making the relationship from the LoginHistory to
