mysql - 将 Plat Framework 1.2.7 升级到 1.5.2 后出现 MySQLIntegrityConstraintViolationException
问题描述
由于服务器上的 Java 和分发更新,我需要更新我的 Play Framework 1 应用程序。
在对 JDK 1.8 进行必要的更改后,一切似乎都正常了。但是,插入新记录时出现以下错误。
08:49:44,922 ERROR ~ Error during device update (Job): org.hibernate.exception.ConstraintViolationException: could not execute statement
javax.persistence.PersistenceException: org.hibernate.exception.ConstraintViolationException: could not execute statement
at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:154)
at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:181)
at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:188)
at org.hibernate.internal.SessionImpl.doFlush(SessionImpl.java:1460)
at org.hibernate.internal.SessionImpl.flush(SessionImpl.java:1440)
at play.db.jpa.JPABase._save(JPABase.java:58)
at play.db.jpa.GenericModel.create(GenericModel.java:375)
at models.Device.createDevice(Device.java:154)
at logic.helpers.DevicePerformer.doJobWithResult(DevicePerformer.java:104)
at logic.helpers.DevicePerformer.doJobWithResult(DevicePerformer.java:1)
at play.jobs.Job$2.apply(Job.java:224)
at play.db.jpa.JPA.withTransaction(JPA.java:285)
at play.db.jpa.JPA.withinFilter(JPA.java:238)
at play.db.jpa.JPAPlugin$TransactionalFilter.withinFilter(JPAPlugin.java:304)
at play.jobs.Job.withinFilter(Job.java:201)
at play.jobs.Job.call(Job.java:220)
at play.jobs.Job$1.call(Job.java:135)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.hibernate.exception.ConstraintViolationException: could not execute statement
at org.hibernate.exception.internal.SQLExceptionTypeDelegate.convert(SQLExceptionTypeDelegate.java:59)
at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:42)
at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:113)
at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:99)
at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:178)
at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:3171)
at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:3686)
at org.hibernate.action.internal.EntityInsertAction.execute(EntityInsertAction.java:90)
at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:604)
at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:478)
at org.hibernate.event.internal.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:380)
at org.hibernate.event.internal.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:39)
at org.hibernate.internal.SessionImpl.doFlush(SessionImpl.java:1454)
... 19 more
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '215' for key 'PRIMARY'
at com.mysql.jdbc.Util.handleNewInstance(Util.java:425)
at com.mysql.jdbc.Util.getInstance(Util.java:408)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:936)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3976)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3912)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2530)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2683)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2486)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1858)
at com.mysql.jdbc.PreparedStatement.executeUpdateInternal(PreparedStatement.java:2079)
at com.mysql.jdbc.PreparedStatement.executeUpdateInternal(PreparedStatement.java:2013)
at com.mysql.jdbc.PreparedStatement.executeLargeUpdate(PreparedStatement.java:5104)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1998)
at com.zaxxer.hikari.pool.ProxyPreparedStatement.executeUpdate(ProxyPreparedStatement.java:61)
at com.zaxxer.hikari.pool.HikariProxyPreparedStatement.executeUpdate(HikariProxyPreparedStatement.java)
at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:175)
... 27 more
MySQL 告诉我下一个索引是 44806,这是我所期望的。
我有两台服务器,当只运行旧代码(Play 1.2.7)时,它工作正常,并按预期给了我一个 ID。两台服务器使用相同的数据库。
新实现给出了低值(在下面的示例中为 215),因此不能使用数据库中的值,而是使用其他值。我确实注意到一个名为 hibernate_sequence 的表带有一个“next_val”字段,它给出的值接近215。它有 25 行,其中一列具有所有相同的数字。
新的 Hibernate 实现是否发生了某些变化,因此我需要更改某些内容以再次使用“下一个自动索引”?
解决方案
不同之处在于 Hibernate 5 未指定生成策略导致 Hibernate 使用自己的策略。
可以通过以下注释来使用 MySQL 值:
@GeneratedValue(strategy = GenerationType.IDENTITY)
推荐阅读
- angular - 如何从 Angular 引用 Eclipse 本地部署的 Spring 应用程序?
- html - css 过渡(悬停和之后)
- python - 神经网络反向传递中的形状未对齐错误
- r - 将数据表列中的值四舍五入到最接近的 50
- r - [ data$group == c("A","B")] 和 [ data$group == "A" | 有什么区别?数据$group == "B" ]?
- javascript - 什么会导致 screen.availHeight 改变?
- sql - 获取具有日期范围的表中每个日期的值
- python - Python函数注释:方法中未定义类
- mysql - 公司中的父子站分层
- loops - 从 Jinja2 中的变量列表访问全局列表