# HG changeset patch # User Todd Larsen # Date 1210286087 0 # Node ID 7947bd33ebbf3f09273a5bb546138741828a8c22 # Parent bdb96b9afe8ef00f3c009f68c26a8a0e39a7ecce Clarify back-reference relations the same way that they are documented for the User model in user.py. Review: http://codereviews.googleopensourceprograms.com/81 diff -r bdb96b9afe8e -r 7947bd33ebbf soc/models/administrator.py --- a/soc/models/administrator.py Thu May 08 22:29:31 2008 +0000 +++ b/soc/models/administrator.py Thu May 08 22:34:47 2008 +0000 @@ -30,7 +30,8 @@ class Administrator(db.Model): """Administrator details for a specific Program. - An Administrator entity participates in a number of relationships: + An Administrator entity participates in the following relationships + implemented as a db.ReferenceProperty elsewhere in another db.Model: host) an optional 1:1 relationship associating generic Administrator details and capabilities with a specific Host. This relation is diff -r bdb96b9afe8e -r 7947bd33ebbf soc/models/person.py --- a/soc/models/person.py Thu May 08 22:29:31 2008 +0000 +++ b/soc/models/person.py Thu May 08 22:34:47 2008 +0000 @@ -41,7 +41,8 @@ other Persons in roles that "need to know" this information. How these fields are revealed is usually covered by Program terms of service. - A Person entity participates in a number of relationships: + A Person entity participates in the following relationships implemented + as a db.ReferenceProperty elsewhere in another db.Model: author) a 1:1 relationship of Person details for a specific Author. This relation is implemented as the 'author' back-reference Query of @@ -59,8 +60,7 @@ #: exist unassociated from a login identity and credentials. The #: back-reference in the User model is a Query named 'persons'. user = db.ReferenceProperty(reference_class=models.user.User, - required=True, - collection_name="persons") + required=True, collection_name="persons") #==================================================================== # (public) name information