javax.jdo.JDOUserException: The column "customer_type_id" was set to multiple different values in this SQL statement. This is probably because the schema mapping uses a single column for multiple fields on the assumption that the fields will always store the same underlying value, but the assumption was broken.

Oracle Community | 3004 | 1 decade ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    1 sided mapping of existing schema

    Oracle Community | 1 decade ago | 3004
    javax.jdo.JDOUserException: The column "customer_type_id" was set to multiple different values in this SQL statement. This is probably because the schema mapping uses a single column for multiple fields on the assumption that the fields will always store the same underlying value, but the assumption was broken.
  2. 0

    Locking error???

    Oracle Community | 2 decades ago | 3004
    javax.jdo.JDOUserException: An instance was concurrently modified in another transaction (optimistic lock #: 60). FailedObject: com.almostthere.business.data.User#24
  3. 0

    change of pk-field fails...

    Oracle Community | 2 decades ago | 3004
    javax.jdo.JDOUserException: An instance was concurrently modified in another transaction (optimistic lock #: 17). FailedObject: de.cg.cornea.data.ClinicID@a308b881: name=Helios Klinik Buch
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Insert failing

    Oracle Community | 2 decades ago | 3004
    javax.jdo.JDOUserException: The column "PARAM_KEY_ID" was set to multiple different values in this SQL statement. This is probably because the schema mapping uses a single column for multiple fields on the assumption that the fields will always store the same underlying value, but the assumption was broken.
  6. 0

    Runtime error

    Oracle Community | 1 decade ago | 3004
    javax.jdo.JDOUserException: No database mapping was found for type "class com.vwfs.Recording"; all persistent types must be registered in the database; this is done automatically through the SchemaTool.

    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. javax.jdo.JDOUserException

      The column "customer_type_id" was set to multiple different values in this SQL statement. This is probably because the schema mapping uses a single column for multiple fields on the assumption that the fields will always store the same underlying value, but the assumption was broken.

      at com.solarmetric.kodo.runtime.PersistenceManagerImpl.flush()
    2. com.solarmetric.kodo
      PersistenceManagerImpl.commit
      1. com.solarmetric.kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:547)
      2. com.solarmetric.kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:393)
      2 frames
    3. com.vwfs
      Testkodo.main
      1. com.vwfs.Customer.save(Customer.java:342)
      2. com.vwfs.Testkodo.runTest2(Testkodo.java:115)
      3. com.vwfs.Testkodo.main(Testkodo.java:23)
      3 frames