From 82eb9de99335c0032986fb3273f9951756205fb9 Mon Sep 17 00:00:00 2001 From: Dan McGee Date: Mon, 4 Oct 2010 17:44:40 -0500 Subject: Make user profile a OneToOneField We had this set up as a unique ForeignKey before, which adds some indirection due to the RelatedManager object being there. By making it a OneToOneField, we can get the profile object directly, enforce uniqueness, and also use it in select_related() calls to make our profiles page a bit more efficient. Signed-off-by: Dan McGee --- devel/management/commands/reporead.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'devel/management/commands/reporead.py') diff --git a/devel/management/commands/reporead.py b/devel/management/commands/reporead.py index 544c4ecb..f7dac9ae 100644 --- a/devel/management/commands/reporead.py +++ b/devel/management/commands/reporead.py @@ -130,7 +130,7 @@ def find_user(userstring): def user_email(): return User.objects.get(email=email) def profile_email(): - return User.objects.get(userprofile_user__public_email=email) + return User.objects.get(userprofile__public_email=email) def user_name(): # yes, a bit odd but this is the easiest way since we can't always be # sure how to split the name. Ensure every 'token' appears in at least -- cgit v1.2.3