bug #7349
RegistrationPopupEditor fails saving new References with new Team with 2 new memers
Start date:
04/13/2018
Due date:
% Done:
100%
Severity:
critical
Found in Version:
Description
habe den Eindruck, dass es wieder an dem neuen Team von 2 neuen Autoren liegt.
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry 'ec10dd7e-1dc1-4ac7-9e0b-a214838f035f' for key 'UK_n0wqwh4csr4mejfjo8k368n6r'
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:404)
at com.mysql.jdbc.Util.getInstance(Util.java:387)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:932)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3878)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3814)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2478)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2625)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2551)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1861)
at com.mysql.jdbc.PreparedStatement.executeUpdateInternal(PreparedStatement.java:2073)
at com.mysql.jdbc.PreparedStatement.executeUpdateInternal(PreparedStatement.java:2009)
at com.mysql.jdbc.PreparedStatement.executeLargeUpdate(PreparedStatement.java:5094)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1994)
at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeUpdate(NewProxyPreparedStatement.java:384)
at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:204)
... 118 more
Associated revisions
ref #7349 prevent from setting nbew persons as value to person select - fixes problem with person fields being mixed up
History
#1 Updated by Andreas Kohlbecker over 2 years ago
- Tags set to phycobank
- Project changed from PhycoBank to Edit
- Category set to cdm-vaadin
- Status changed from New to In Progress
- Target version set to Release 5.0
- Severity set to critical
#2 Updated by Andreas Kohlbecker over 2 years ago
- % Done changed from 0 to 100
This was a quite strange bug.
As long as the new person objects where set as value to the lazy select the contact and other fields have been mixed up between the first person crated and of the second one. This was causing both person objects sharing the same contact object.
#3 Updated by Andreas Kohlbecker over 2 years ago
- Status changed from In Progress to Closed
