On Nov 8, 2007 2:21 PM, Jonathan Buchanan <[EMAIL PROTECTED]> wrote: > On this particular point, from the perspective of the reusable > applications themselves, you don't need to worry about merging profile > models, even if you are potentially working with many of them in your > overall project. Going with the forum example, if your forum > application defines its own profile Model which addresses all of its > specific needs, it doesn't benefit it in any way if it has access to > some kind of merged profile instead - it does, however, introduce the > potential for conflicts. > > Personally, I never rely on the AUTH_PROFILE_MODEL setting and the > User.get_profile method in reusable applications, I only use those in > my main project. It's not a lot of work to add a method to your > application's profile Manager to load and cache a user's > application-specific profile in a manner similar to User.get_profile. > Since I'm actually working on a reusable forum application at the > moment, here's an example of what I mean:
But what about if your forum have a field for an Jabber account or ICQ UIN and a blog (whatever) application has the same? Synchronize them using signals? Isn't this not very safe solution? -- 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 -~----------~----~----~----~------~----~------~--~---
