kodo.util.UnsupportedOptionException

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.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web6

  • via Oracle Community by 3004, 1 year 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.
  • via Oracle Community by 3004, 1 year 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.
  • via Oracle Community by 3004, 11 months ago
    Unable to create second class object proxy for type: "class be.li3.util.history.LongHist".
  • Stack trace

    • kodo.util.UnsupportedOptionException: 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. at kodo.jdbc.query.SQLQuery.newInMemoryQueryExecutor(SQLQuery.java:117) at kodo.query.AbstractQuery.internalCompile(AbstractQuery.java:545) at kodo.query.AbstractQuery.getAccessPathMetaDatas(AbstractQuery.java:938)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.