1. Home
  2. »
  3. Exception types
  4. »
  5. kodo
  6. »
  7. kodo.util
  8. »
  9. UnsupportedOptionException

UnsupportedOptionException crashes

Collection of 3 web pages containing stack traces of kodo.util.UnsupportedOptionException

Find a solution to your bug here

This list contains all the bugs that lead to this exception. Click through to see the discussions about them.

  1. Map mapping / UnsupportedOptionException

    via Oracle Community by 30042 years ago
    Unable to create second class object proxy for type: "class be.li3.util.history.LongHist".
  2. UnsupportedOption Exception while executing Query

    via Oracle Community by 30042 years ago
    kodo.jdbc.SQL language queries cannot be executed in-memory. Either set the javax.jdo.option.IgnoreCache property to true, set the kodo.FlushBeforeQueries property to true, or execute the query before modifying objects within the transaction.
  3. using SQL in Query in 3.0.0

    via Oracle Community by 30042 years ago
    kodo.jdbc.SQL language queries cannot be executed in-memory. Either set the javax.jdo.option.IgnoreCache property to true, set the kodo.FlushBeforeQueries property to true, or execute the query before modifying objects within the transaction.

or use our map

We've collected millions of stack traces from the web.

We visualize these cases as a tree for easy understanding. We place your stack trace on this tree so you can find similar ones. The top nodes are generic cases, the leafs are the specific stack traces.

Paste your stack trace to find solutions with our map.