As far as I know, it is more suitable to use a NoSQL document database such as mongodb. Of course, writing a demo does not consider scalability. After the schema of the relational database is fixed, it will be difficult to expand. For example, the attribute items of daggers and shields are different, and it will be awkward to store them in a relational way. If it is an online game, consider the need for horizontal expansion as the number of users increases in the future. MySQL also has many limitations, so you must consider using a database designed for clusters.
A record is stored for each piece of equipment, and each column lists the attribute configuration of the equipment. The database only does storage, and the representation or performance is left to the server and client to parse and apply.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
As far as I know, it is more suitable to use a NoSQL document database such as mongodb. Of course, writing a demo does not consider scalability.
After the schema of the relational database is fixed, it will be difficult to expand. For example, the attribute items of daggers and shields are different, and it will be awkward to store them in a relational way.
If it is an online game, consider the need for horizontal expansion as the number of users increases in the future. MySQL also has many limitations, so you must consider using a database designed for clusters.
A record is stored for each piece of equipment, and each column lists the attribute configuration of the equipment. The database only does storage, and the representation or performance is left to the server and client to parse and apply.