does not follow the hibernate有关系的。 MySQLIntegrityConstraintViolationException 外键约束冲突。 是数据库层面出错了。可以通过堆栈确定一下调用过程，如果没有insert/update operation.
I don’t see any reason behind the logic you gave. You can use error logictry catch包起来，在catch中增加条件断点e.getClass().getName().contains("MySQLIntegrityConstraintViolationException") When an error occurs and analyze the existing data, I think the problem will be located soon.
MAC is a unique index. The exception reported here refers to a unique index conflict caused by inserting the same value, which is an exception at the database level.
As for why this exception is caused, it depends on how the code is written.
It is suspected that there is a problem with this polling process. The second request may have been sent before the first request has returned, and then the parameters passed in are repeated, resulting in a repeated insertion exception.
The above two points are very clear... This is an error caused by your failure to control the business level. Specifically, only people with code can solve it.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
This problem will not occur if
does not follow the
hibernate有关系的。MySQLIntegrityConstraintViolationException外键约束冲突。是数据库层面出错了。可以通过堆栈确定一下调用过程，如果没有
insert/updateoperation.I don’t see any reason behind the logic you gave. You can use error logic
try catch包起来，在catch中增加条件断点e.getClass().getName().contains("MySQLIntegrityConstraintViolationException")When an error occurs and analyze the existing data, I think the problem will be located soon.
MAC is a unique index. The exception reported here refers to a unique index conflict caused by inserting the same value, which is an exception at the database level.
As for why this exception is caused, it depends on how the code is written.
It is suspected that there is a problem with this polling process. The second request may have been sent before the first request has returned, and then the parameters passed in are repeated, resulting in a repeated insertion exception.
The above two points are very clear... This is an error caused by your failure to control the business level. Specifically, only people with code can solve it.