Michael; Think of it this way: the auth model is just one way to provide authentication into your architecture. It wouldn't make much sense to have too much more information about the person inside of this model. There is an effort to try to be able to extend models, but as far as I know it has been a difficult forge forward because databases don't work that way. The tie to another model is perfectly natural.
As I am still thinking about this you wouldn't want to inherit the code anyway. If you want the cleanest implementation of your code you wouldn't want to have 2 different types (or the possibility thereof) of authentication. What I was saying in my first post is that you don't need to use any of the contrib applications. In fact, you can go ahead and look directly into the auth code and try to rewrite it with all the extras that you would like to put into it. I personally think you would be making yourself crazy just to save a table in your database, but if that is your cup of tea... Evert, take a look at the Model Inheritance branch: http://code.djangoproject.com/wiki/ModelInheritance it looks exciting, but a huge undertaking for whoever is working on it. I would be exciting to see and could save a lot of application code really. It definatly doesn't look like it would be ready before 1.0 On Tue, Mar 4, 2008 at 10:21 PM, Michael Irani <[EMAIL PROTECTED]> wrote: > > One thing I dislike about the approach that's being pushed by the > community, which is to have a one-to-one relationship between > auth.User and your own 'Profile' model (or whatever you want to call > it) adding all the functionality and relationships to the user-created > Model is a bit much. I mean yes it's convenient to use auth.User's > prebuilt functionality, but if you're building for the future and want > to start off in the right place, this method kind of starts your code > in an awkward place. The data model with this approach just feels > wrong... The right way to do it is to have two different tables link > to eachother and have the database make the bindings for you. I know > this simplifies the code a lot and that the DB will probably do a good > job with this lookup, but still seems a little awkward to me... > > > > > --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
