Hi, Django have known trouble with default User object, which is not always appropriate for all applications, when they need additional information. Of course, we have solution with user profile and get_profile, but it is not very nice solution and have imperfections: ;-) - it is not fetched automatically with User object (it can be, but with a lot of code) - you must think about creation of it - (main trouble) if you have absolutely different applications, which use profile for their own purposes, you need to merge their Profile models - trouble is in the updating of this thing (f.e., you have forum, created by someone and integrated in your project, and you definitely want to have updates).
I thought a lot about this situation and I think that I see light in the end of tunnel - making User model dynamic and configurable via settings (or whatever). It will be not very hard to implement, it will speed up and simplify (from my point of view) things a lot and I don't see any serious drawbacks. What do you think about this? If this sounds reasonable, I'm happy to open a ticket and create a patch for this. -- Alexander --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
