Log in to register the module data sheet I used to think that simple, is nothing more than user name, password, UID, registration time and so on. But I now, but found that the module is really not simple, the data sheet of this module is also followed by some other modules, if not done well, will affect other modules.
For example: Now any site will have security aspects, to prevent malicious registration (for the same IP), prohibit IP and other such security modules, or consider the data of the following several sites in the same situation, but also user rights and third-party login AH and so on.
How are your datasheets created, or do you have a relatively fixed data table template for login registration modules for the situation I mentioned above?
Trouble, everybody.
Reply content:
Log in to register the module data sheet I used to think that simple, is nothing more than user name, password, UID, registration time and so on. But I now, but found that the module is really not simple, the data sheet of this module is also followed by some other modules, if not done well, will affect other modules.
For example: Now any site will have security aspects, to prevent malicious registration (for the same IP), prohibit IP and other such security modules, or consider the data of the following several sites in the same situation, but also user rights and third-party login AH and so on.
How are your datasheets created, or do you have a relatively fixed data table template for login registration modules for the situation I mentioned above?
Trouble, everybody.
Two tables user and User_extend
User store ID, username, password, mobile phone and other common information
User_extend store Birthdays, points, etc. infrequently used information