3 ms·
You could already extend the user model with a OneToOne relation plus setting in settings.py that was supported in the official Django distribution. But the way
by rheide 14y ago
You could already extend the user model with a OneToOne relation plus setting in settings.py that was supported in the official Django distribution. But the way that was handled was a bit hacky so I'm glad they changed it too.
- wahnfrieden 14y agoYea and incur an extra DB lookup every time. This is very welcome.
- the_cat_kittles 14y agonot to mention tastypie headaches when trying to update nested resources (user->userprofile->something else)
- zalew 14y agoBut you still were forced to use obligatory auth.User fields like username/email, etc., while there are quite a few use cases when you curse it and the only choices were either making some really weird workarounds or dropping User altogether. Russel's solution is meant to solve this problem.