kodo.util.FatalUserException: Attempt to set column "BASECLASSPC.REFERENCEDCLASS_JDOID" to two different values: (null)"null", (class java.lang.Long)"251" This can occur when you fail to set both sides of a two-sided relation between objects, or when you map different fields to the same column, but you do not keep the values of these fields in synch.

Oracle Community | 3004 | 1 decade ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    Kodo 3.3.3, InverseManager, 1:1 Relation

    Oracle Community | 1 decade ago | 3004
    kodo.util.FatalUserException: Attempt to set column "BASECLASSPC.REFERENCEDCLASS_JDOID" to two different values: (null)"null", (class java.lang.Long)"251" This can occur when you fail to set both sides of a two-sided relation between objects, or when you map different fields to the same column, but you do not keep the values of these fields in synch.

    Root Cause Analysis

    1. kodo.util.FatalUserException

      Attempt to set column "BASECLASSPC.REFERENCEDCLASS_JDOID" to two different values: (null)"null", (class java.lang.Long)"251" This can occur when you fail to set both sides of a two-sided relation between objects, or when you map different fields to the same column, but you do not keep the values of these fields in synch.

      at kodo.jdbc.sql.PrimaryRow.setObject()
    2. kodo.jdbc.sql
      PrimaryRow.setForeignKey
      1. kodo.jdbc.sql.PrimaryRow.setObject(PrimaryRow.java:215)
      2. kodo.jdbc.sql.RowImpl.flushJoinValues(RowImpl.java:267)
      3. kodo.jdbc.sql.RowImpl.flushForeignKey(RowImpl.java:189)
      4. kodo.jdbc.sql.RowImpl.setForeignKey(RowImpl.java:158)
      5. kodo.jdbc.sql.PrimaryRow.setForeignKey(PrimaryRow.java:128)
      5 frames