I am currently preparing a Django based site. For simplicity it assumes that this is a simple community site where users can log in and write messages to other users.
To use my current choice build user-model or to create something of my own I do not need more than buildin Everything, it sees me, that I create a single user model and use the build only to access the admin backend. Is there anything wrong with my reflection? Is there something wrong with my reflection? Yes. My current choice is to use the buildin user's model or have some weather to make their own. Not like a third. Everything will be put in a UserProfile right. The use of buildin only for the creation and production of my one user model Do this: If you want to store additional information related to your users, DJGOGO for this purpose Provides a method for specifying a site-specific related model - the "user profile" is called. user : no username will be available -Mail address is username), but you can set an intuitive name of your choice, which is used by many users (such as Facebook) Additionally, I do not need the permission system, because others are not based on reach groups. Will be there. Therefore, I will just end up using the Build user using the email, first name, last name and password field, and everything else will be placed in a UserProfile. On the other hand, the build user system works on the backend of the site, because there is a chance I will need a group based permission system.
Comments
Post a Comment