Dan McGee 82eb9de993 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>		2010-10-04 17:44:40 -05:00
..
fixtures	Update MirrorProtocol fixture data	2010-09-30 14:36:38 -05:00
migrations	Make user profile a OneToOneField	2010-10-04 17:44:40 -05:00
templatetags	Get secure/unsecure checking actually working	2010-09-22 23:16:13 -05:00
__init__.py	Moved models around	2008-03-08 00:13:41 -08:00
admin.py	Allow donors to be invisible	2010-10-01 13:05:22 -05:00
context_processors.py	Get secure/unsecure checking actually working	2010-09-22 23:16:13 -05:00
middleware.py	Remove AutoUserMiddleware	2010-06-20 23:31:34 -05:00
models.py	Make user profile a OneToOneField	2010-10-04 17:44:40 -05:00
utils.py	Make the cache_function key a bit more descriptive	2010-07-10 16:23:36 -05:00