> May be better way to use ``OneToOneField`` with proper > ``related_name`` like "profile" for example. Than profile can be > accessed very simple ``user.pofile``. and its creation machinery leave > to profile app author?
Right, I knew there was a fifth alternative I forgot to mention. ;-) This doesn't remove the need to catch the DoesNotExist-exception everywhere. Additionally it does not work when trying to create reusable applications that need to have access to some profile. Greetings, David Danier --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
