On Mon, Aug 17, 2009 at 11:57 AM, Jonas Obrist<ojiido...@gmail.com> wrote:
>
> Hey Jacob
>
> Thanks for your opinion on this, didn't know django had this feature
> once. But I just can't get it out of my head that there's gotta be a
> better solution than this profile-extending... It just seems ridiculous
> to me that half of the user properties is in one table and the other
> half in the other one. And I don't like the template variables looking
> like {{ request.user.user.someproperty }} and {{
> request.user.some_other_property }}.What about using __getattr__() to delegate attribute acces from one model to the other? (if that's the central problem). -- Leo Soto M. http://blog.leosoto.com --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
