Apache JDO Project - [jira] Closed: (JDO-100) Insert request failed ... because it would have caused a dupl

This is Interesting: Free IT Magazines  
Home > Archive > Apache JDO Project > October 2005 > [jira] Closed: (JDO-100) Insert request failed ... because it would have caused a dupl





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author [jira] Closed: (JDO-100) Insert request failed ... because it would have caused a dupl
Michelle Caisse (JIRA)

2005-10-31, 5:45 pm

[ http://issues.apache.org/jira/browse/JDO-100?page=all ]

Michelle Caisse closed JDO-100:
-------------------------------


> Insert request failed ... because it would have caused a duplicate key value
> ----------------------------------------------------------------------------
>
> Key: JDO-100
> URL: http://issues.apache.org/jira/browse/JDO-100
> Project: JDO
> Type: Bug
> Components: tck20
> Reporter: Michelle Caisse


>
> testSingleFieldIdentityInitializedDate and
> testSingleFieldIdentityDate(org.apache.jdo.tck.api.persistencecapable.CopyKeyFieldsFromObjectId)javax.jdo.JDODataStoreException: Insert request failed: INSERT INTO applicationidentity0.PCPOINTSINGLEFIELDDATE (Y,X,ID) VALUES (?,?,?)
> at org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:329)
> at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:1750)
> at org.jpox.store.StoreManager.insert(StoreManager.java:663)
> at org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3090)
> at org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3063)
> at org.jpox.AbstractPersistenceManager. internalMakePersistent(AbstractPersisten
ceManager.java:1012)
> at org.jpox.AbstractPersistenceManager. makePersistent(AbstractPersistenceManage
r.java:1048)
> at org.apache.jdo.tck.api.persistencecapable.AbstractPersistenceCapableTest. makePersistent(AbstractPersistenceCapabl
eTest.java:41)
> at org.apache.jdo.tck.api.persistencecapable.CopyKeyFieldsFromObjectId. singleFieldIdentity(CopyKeyFieldsFromObj
ectId.java:156)
> at org.apache.jdo.tck.api.persistencecapable.CopyKeyFieldsFromObjectId. testSingleFieldIdentityDate(CopyKeyField
sFromObjectId.java:143)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at org.apache.jdo.tck.JDO_Test.runBare(JDO_Test.java:197)
> at org.apache.jdo.tck.util.BatchTestRunner.start(BatchTestRunner.java:128)
> at org.apache.jdo.tck.util.BatchTestRunner.main(BatchTestRunner.java:106)
> NestedThrowablesStackTrace:
> ERROR 23505: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'PCPNT_SFD_PK' defined on 'PCPOINTSINGLEFIELDDATE'.
> at org.apache.derby.iapi.error.StandardException.newException(StandardException.java)
> at org.apache.derby.impl.sql.execute.IndexChanger.insertAndCheckDups(IndexChanger.java)
> at org.apache.derby.impl.sql.execute.IndexChanger.doInsert(IndexChanger.java)
> at org.apache.derby.impl.sql.execute.IndexChanger.insert(IndexChanger.java)
> at org.apache.derby.impl.sql.execute.IndexSetChanger.insert(IndexSetChanger.java)
> at org.apache.derby.impl.sql.execute.RowChangerImpl.insertRow(RowChangerImpl.java)
> at org.apache.derby.impl.sql.execute.InsertResultSet.normalInsertCore(InsertResultSet.java)
> at org.apache.derby.impl.sql.execute.InsertResultSet.open(InsertResultSet.java)
> at org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(EmbedPreparedStatement.java)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(EmbedPreparedStatement.java)
> at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeUpdate(NewProxyPreparedStatement.java:443)


--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com