My model has an owned one-to-one relationship just like in the Employee ContactInfo example. I can create the owning instance (Employee) with a ContactInfo, but my problem is, that I cannot update it afterwards. There is no exception, but the employee's contactInfo will remain the old one. Yet, when I have a look at the datastore, the new contact info is there.
I can imagine, why this is: there are two distinct entities in the datastore, one for employee, and one for the contact infos. The relationship is made up by the key of ContactInfo, which contains the key of the owning employee. Now, when there is more than one contact info entity for an employee, how should the data store know which one to take for the employee? Anybody having the same problem, or am I missing anything? Regards, Nick -- 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.
