Although the previous use of tinyint and other preservation, but found that business logic is often changed, the number sequence is disrupted, and the naked eye becomes difficult to identify, if you directly execute SQL statements in the database also check the corresponding constant configuration instructions
It is found that many foreign open source programs use character store status.
Reply content:
Although the previous use of tinyint and other preservation, but found that business logic is often changed, the number sequence is disrupted, and the naked eye becomes difficult to identify, if you directly execute SQL statements in the database also check the corresponding constant configuration instructions
It is found that many foreign open source programs use character store status.
Nobody dares to pack a ticket. Business is not changed, the best database design is to use string storage (although performance may be sacrificed)
Recommended enumeration Typesenum
This scenario can be considered with enumerations: Enum types
Comment Write the notes clearly, do not overwrite the previous can be
Enum or tinyint
Useint