From the perspective of the third paradigm, the three columns of main subject total score, secondary subject total score, and total score are data that depend on other columns and should not be placed in the database table as separate columns.
If you consider that the pressure of data reading is high and you don’t want to do calculations on the application server or database side, you can store it in the table as redundant columns. In the scenario mentioned above, the number of modifications to students' grades after they are entered should be very few. Therefore, the update cost of redundant columns is low. It is a typical situation of more reads and less writes. Therefore, there is overall pressure on the server due to redundant columns. will be lower.
It depends on whether you insert a lot of data or read a lot of results; When you insert a lot of data, put the calculation in the view, and when you read a lot of data, put the SQL calculation results in the table, but the reading pressure It is much lower than insertion. This ratio still needs to be weighed. It is recommended to choose to place it in the view.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
From the perspective of the third paradigm, the three columns of main subject total score, secondary subject total score, and total score are data that depend on other columns and should not be placed in the database table as separate columns.
If you consider that the pressure of data reading is high and you don’t want to do calculations on the application server or database side, you can store it in the table as redundant columns. In the scenario mentioned above, the number of modifications to students' grades after they are entered should be very few. Therefore, the update cost of redundant columns is low. It is a typical situation of more reads and less writes. Therefore, there is overall pressure on the server due to redundant columns. will be lower.
It depends on whether you insert a lot of data or read a lot of results;
When you insert a lot of data, put the calculation in the view, and when you read a lot of data, put the SQL calculation results in the table, but the reading pressure It is much lower than insertion. This ratio still needs to be weighed. It is recommended to choose to place it in the view.