Although tinyint has been used for storage in the past, but if the business logic is often changed, the order of numbers is disrupted, and it becomes difficult to identify with the naked eye, if you execute SQL statements directly in the database and check the constant configuration, it means that many open-source foreign programs use character storage. Although tinyint has been used for storage in the past, but if the business logic is often changed, the order of numbers is disrupted, and it becomes difficult to identify with the naked eye, if you execute SQL statements directly in the database, check the constant configuration instructions.
It is found that many open-source programs outside China use character storage.
Reply content:
Although tinyint has been used for storage in the past, but if the business logic is often changed, the order of numbers is disrupted, and it becomes difficult to identify with the naked eye, if you execute SQL statements directly in the database, check the constant configuration instructions.
It is found that many open-source programs outside China use character storage.
No one dares to package the ticket without changing the business. The best database design is to store it using strings (although it may sacrifice performance)
Enumeration type is recommended.Enum
In this case, you can use enumeration: enum type.
Comment writes the comments clearly. do not overwrite the previous ones.
Enum or tinyint
UseInt