want to use django to develop a resume recruitment system, ask which corporate member and individual member. Is it better to use one User model or to design two?
I have now created a new users app,
class User (AbstractUser):
xxx
then the next step. Both corporate and individual members use this one to design?
still have to go and set up another users app?
do you have any good ideas?
develop two different types of membership systems for the first time. Not really.
I think if two kinds of members intersect, if there are more members, do it in one app, and then the classes of the two models inherit the same base class. If there is not much overlap, it is OK to separate, and it is also convenient for cooperative development.
individuals don't like to use their User. I will create a new class, then classify the two into the new class and distinguish them with type.
I made a recruitment website a long time ago, in which corporate members and individual members are separate. But I remember that the street network was put together, and they did an enterprise email authentication
.it's up to you. If you want to keep it simple, separate it
.Previous: Let me first ask you how to use nginx to tell the difference between a mobile phone and a pc.
the server is written by nginx + uwsgi + djano, the project is relatively old, and it has been found to be unresponsive recently. After investigation, it is found that the uwsgi queue is slow and full, eliminating the problem of excessive number of reque...