So you are worried that a user will be deleted and his key will still be linked to the book? You can't rely on the database to do that work for you. You can do this two ways, worry about it, and when you delete a user, make sure you delete it's key from every book. Or don't worry about it. If you do your queries right, having a non existent user stored in a book won't cause any problems. But I would recommend removing it when a user gets deleted.
On Feb 7, 3:11 pm, Arjan <arjan.br...@gmail.com> wrote: > Will, > Thanks for the hint. > When i use the User key (a String) as the reference from the Book to the > User object, that would mean that the referential integrity is not enforced > by the database. I understand that it would work, but it feels kind of > strange. > Is there a way to maintain the referential integrity on between the classes? > Regards. -- 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-java@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.
