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
-~----------~----~----~----~------~----~------~--~---
