kodo.util.FatalUserException: Attempt to set column "ADDRESS.P_ID" to two different values: (null)"null", (class java.lang.Long)"1'750" 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
  1. 0

    field representing a FK

    Oracle Community | 1 decade ago | 3004
    kodo.util.FatalUserException: Attempt to set column "ADDRESS.P_ID" to two different values: (null)"null", (class java.lang.Long)"1'750" 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.
  2. 0

    pre-assigning sequence-assigned PK values

    Oracle Community | 1 decade ago | 3004
    kodo.util.FatalUserException: Attempt to set column "CHILD.parentId" to two different values: (class java.lang.Integer)"0", (class java.lang.Integer)"2,503" 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.
  3. 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.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 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.
  6. 0

    Horizontal Mapping and Flat mapping with Metadata Value Indicator

    Oracle Community | 1 decade ago | 3004
    kodo.util.FatalUserException: Attempt to set column "B.FOO" to two different values: (java.lang.Object)"java.lang.Object@2f608ac2", (java.lang.String)"wilma" 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.runtime.VRow.setObjectInternal(VRow.java(Compiled Code)) at kodo.jdbc.sql.AbstractRow.setObject(AbstractRow.java(Compiled Code))

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. kodo.util.FatalUserException

      Attempt to set column "ADDRESS.P_ID" to two different values: (null)"null", (class java.lang.Long)"1'750" 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
      RowImpl.getSQL
      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.generateSQL(PrimaryRow.java:238)
      6. kodo.jdbc.sql.RowImpl.getSQL(RowImpl.java:681)
      6 frames
    3. kodo.jdbc.runtime
      JDBCStoreManager.flush
      1. kodo.jdbc.runtime.PreparedStatementManager.flushInternal(PreparedStatementManager.java:137)
      2. kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java:84)
      3. kodo.jdbc.runtime.UpdateManagerImpl.flushGraph(UpdateManagerImpl.java:709)
      4. kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:178)
      5. kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:95)
      6. kodo.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:609)
      6 frames
    4. kodo.runtime
      PersistenceManagerImpl.commit
      1. kodo.runtime.DelegatingStoreManager.flush(DelegatingStoreManager.java:153)
      2. kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:1155)
      3. kodo.runtime.PersistenceManagerImpl.flushSafe(PersistenceManagerImpl.java:1038)
      4. kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:965)
      5. kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
      6. kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:625)
      6 frames
    5. kodo
      Main.main
      1. kodo.Main.exec(Main.java:71)
      2. kodo.Main.test1(Main.java:160)
      3. kodo.Main.main(Main.java:26)
      3 frames