Hmmm... I read the subclassing post. As a non-abstract child is essentially a one to one with some syntactical sweetness, I'm still not sure how using a one to one field is better suited than inheritance for extending user.
Rajeev J Sebastion wrote: > Because every app has its own concept/method of how to link info to a > User object, hence that information is best held in other models each > with a FK to the User. Don't see why each model can't do what they want... one to one, inheritance, etc to obtain the same result. Seeking enlightenment as I try to prepare my mind for qsrf --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
