I feel that this constraint may not be achieved.
If you think about it differently, you need to get the relevant rows and make a judgment when performing INSERT, UPDATE, and DELETE on the table.
Another way of thinking: Put the multi-column values to be stored into one column, add a unique constraint to this column, and add an additional attribute identifier for different purposes
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
You can only write check with constraints
I feel that this constraint may not be achieved.
If you think about it differently, you need to get the relevant rows and make a judgment when performing INSERT, UPDATE, and DELETE on the table.
Another way of thinking: Put the multi-column values to be stored into one column, add a unique constraint to this column, and add an additional attribute identifier for different purposes