2 | Option or strategy to disable/skip runtime enhancement checks (to improve load time)?-based compile-time enhancement applied to entity modules (only), so I know these checks |
2 | Why the internal error was thrown? We get this exception sporadic in our TestSuite. We observed this problem on a 32BIT OS. The same compiled export |
2 | Possible issue for default id generator. Technically the generator element is defined as optional (and you don't get a compilation error |
2 | Log4j errorHi, We are using OBjectDB OEM Enhancer as part of our build process and we encountered following log4j error: compile: [echo] Start enhancement of ORS entities for use in ObjectDB [java] log4j:ERROR A "org.apache.log4j.xml.DOMConfigurator" object is not assignable to a "org.apache.log4j.spi |
2 | Embedding ObjectDB on server application issue. Maybe objectdb.jar is available only in compilation and not at runtime. support Support |
2 | Log is almost empty (log level 'trace')) has only database open/close messages, some query.compiler info but nothing more.. Is that right |
2 | object creation during pmf.getPersistenceManager() by hand, we skiped fields initializers which are generated by compiler into each constructor so now |
2 | significant performance decrease If the query string is found in the query program cache - no query compilation is needed |
0 | ObjectDB 2.5.6 a NullPointerException in query compilation. Fixed a memory leak (Negative snapshot user count) in UPDATE queries |
0 | Different behavior for two equal queries components. Navigation should be compiled as LEFT OUTER JOIN to avoid losing results in such cases |
