- Django Design Patterns and Best Practices
- Arun Ravindran
- 131字
- 2021-06-25 21:32:07
Problem details
Out of the box, Django provides a pretty decent user model. You can use it when you create a super user or login to the admin interface. It has a few basic fields, such as full name, username, and email.
However, most real-world projects keep a lot more information about users, such as their address, favorite movies, or their superpower abilities. From Django 1.5 onwards, the default user model can be extended or replaced. However, official docs strongly recommend storing only authentication data even in a custom user model (it belongs to the auth app, after all).
Certain projects need multiple types of users. For example, SuperBook can be used by superheroes and non-superheroes. There might be common fields and some distinctive fields based on the type of user.
- AngularJS Testing Cookbook
- 企業級Java EE架構設計精深實踐
- Instant Apache Stanbol
- SpringMVC+MyBatis快速開發與項目實戰
- Mastering PHP Design Patterns
- Oracle數據庫從入門到運維實戰
- Oracle Database 12c Security Cookbook
- Python貝葉斯分析(第2版)
- Yocto for Raspberry Pi
- ASP.NET程序設計教程
- Learning DHTMLX Suite UI
- 深入淺出Serverless:技術原理與應用實踐
- Haskell Data Analysis Cookbook
- Building Microservices with .NET Core
- Django 3.0入門與實踐