On 8/9/06, Chris Kelly <[EMAIL PROTECTED]> wrote: > If I am understanding correctly now, does this mean I have to manage the > creation of the user profile object (and also any other classes tied to a > user) when I create the user?
Yes; OneToOne requires that an object exist on both ends of the relationship. One easy way to deal with this is to make most or all of the fields on your profile class optional, so you can just create an empty instance and populate it later. -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users -~----------~----~----~----~------~----~------~--~---
