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 --- main/models.py | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'main/models.py') diff --git a/main/models.py b/main/models.py index 79d99e8c..10a77379 100644 --- a/main/models.py +++ b/main/models.py @@ -27,8 +27,7 @@ class UserProfile(models.Model): roles = models.CharField(max_length=255, null=True, blank=True) favorite_distros = models.CharField(max_length=255, null=True, blank=True) picture = models.FileField(upload_to='devs', default='devs/silhouette.png') - user = models.ForeignKey( - User, related_name='userprofile_user', unique=True) + user = models.OneToOneField(User, related_name='userprofile') allowed_repos = models.ManyToManyField('Repo', blank=True) class Meta: db_table = 'user_profiles' -- cgit v1.2.3