From 82eb9de99335c0032986fb3273f9951756205fb9 Mon Sep 17 00:00:00 2001
From: Dan McGee <dan@archlinux.org>
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 <dan@archlinux.org>
---
 templates/public/developer_list.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'templates/public')

diff --git a/templates/public/developer_list.html b/templates/public/developer_list.html
index 61a612c..bb03f43 100644
--- a/templates/public/developer_list.html
+++ b/templates/public/developer_list.html
@@ -11,7 +11,7 @@
 
 <table class="arch-bio-entry">
     {% for dev in dev_list %}
-    {% with dev.get_profile as prof %}
+    {% with dev.userprofile as prof %}
     <tr>
         <td class="pic pic-{{ dev.username }}">
             <img src="{{ prof.picture.url }}" height="125" width="125" alt="Image for {{ prof.alias }}"/>
-- 
cgit v1.2.3-24-g4f1b