Question

I get an MySQLIntegrityConstraintViolationException when saving an object to my database. I know what this error means, but I cannot work around it.

Error: Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '12345' for key 'PRIMARY'

Basically, I want to save course objects to a database. Each course object may have several studypath objects, which can in turn be part of several course objects.

PersistenceManager pm = pmf.getPersistenceManager();
Transaction tx = pm.currentTransaction();

try {
    tx.begin();
    Query query = pm.newQuery(Studypath.class,"studypathID == paramStudypathID");
    query.declareParameters("Integer paramStudypathID");
    query.setUnique(true);
    Studypath dbStudypath = (Studypath)query.execute(12345);

    Studypath detachedStudypath = null;
    if (dbStudypath != null) {
        detachedStudypath = (Studypath)pm.detachCopy(dbStudypath);
    } else {
        Studypath newStudypath = new Studypath();
        // ...
        pm.makePersistent(newStudypath);
        detachedStudypath = (Studypath)pm.detachCopy(newStudypath);
    }

    tx.commit();

    // now I want to add  this detached studypath to my newly created course
    Course c = new Course();
    c.addStudypath(detachedStudypath);

    tx.begin();
    pm.makePersistent(c); // <== error
    tx.commit();
}
catch (Exception e)
{
    //... handle exceptions
}
finally
{
    if (tx.isActive())
    {
        // Error occurred so rollback the transaction
        tx.rollback();
    }
    pm.close();
}

Course.java

@PersistenceCabable
public class Course {
    // ...

    @Persistent
    private Set<Studypath> studypaths;
}

Studypath.java

@PersistenceCabable
public class Studypath {
    // ...

    @Persistent
    @PrimaryKey
    private Integer studypathID;
}

Is there any obvious mistake I’m missing? Thanks in advance!

Update (log):

DEBUG [DataNucleus.Datastore.Native] - SELECT 'Courses.Studypath' AS NUCLEUS_TYPE, ... FROM `STUDYPATH` `A0` WHERE `A0`.`STUDYPATHID` = <12345> // this one already exists
DEBUG [DataNucleus.Datastore.Retrieve] - Execution Time = 0 ms
DEBUG [DataNucleus.Datastore.Retrieve] - Retrieving PreparedStatement for connection "jdbc:mysql://127.0.0.1/database, UserName=user, MySQL-AB JDBC Driver"

DEBUG [DataNucleus.Datastore.Native] - SELECT 'Courses.Course' AS NUCLEUS_TYPE, ... FROM `COURSE` `A0` WHERE `A0`.`COURSEID` = <1111> // there is no such course, thus it gets created
DEBUG [DataNucleus.Datastore.Retrieve] - Execution Time = 1 ms
DEBUG [DataNucleus.Datastore.Retrieve] - Retrieving PreparedStatement for connection "jdbc:mysql://127.0.0.1/database, UserName=user, MySQL-AB JDBC Driver"
DEBUG [DataNucleus.Datastore.Native] - INSERT INTO `COURSE` (...,`COURSEID`) VALUES (...,<1111>)
DEBUG [DataNucleus.Datastore.Persist] - Execution Time = 1 ms (number of rows = 1)
DEBUG [DataNucleus.Datastore.Retrieve] - Closing PreparedStatement org.datanucleus.store.rdbms.ParamLoggingPreparedStatement@3baac1b5

DEBUG [DataNucleus.Datastore.Persist] - The requested statement "INSERT INTO `STUDYPATH` (...) VALUES (...)" has been made batchable
DEBUG [DataNucleus.Datastore.Persist] - Batch has been added to statement "INSERT INTO `STUDYPATH` (...) VALUES (...)" for processing (batch size = 1)
DEBUG [DataNucleus.Datastore.Persist] - Adding statement "INSERT INTO `STUDYPATH` (...) VALUES (...)" to the current batch (new batch size = 2)
DEBUG [DataNucleus.Datastore.Persist] - Batch has been added to statement "INSERT INTO `STUDYPATH` (...) VALUES (...)" for processing (batch size = 2)
DEBUG [DataNucleus.Datastore.Native] - BATCH [INSERT INTO `STUDYPATH` (...,`STUDYPATHID`) VALUES (...,<12345>); INSERT INTO `STUDYPATH` (...,`STUDYPATHID`) VALUES (<54321>)]
ERROR [DataNucleus.Datastore] - Exception thrown

Answer 1

I’m not sure it’s kosher to associate a detached JDO to a transient one. There’s no easy way for the ORM to know the relation is an existing JDO.

If it’s really in the same code path, I’d associate the persistent instance:

c.addStudypath(dbStudypath);

Otherwise I would makePersistent(detachedStudypath) before associating it (assuming your class is @Detachable)