6 | Saving custom list which implements java.util.List fails tracking. > if somehow the internal list gets replaced fully by another list (without filling |
6 | First query takes 4+ minutes to complete" on-persist="false" on-commit="true" /> <dirty-tracking arrays="false" /> </entities> <schema |
6 | JPA Query language support in OBjectDB / Sub query or nested Query Dhamale Inner queries are not supported yet. The issue tracking system contains an up to date list of unsupported JPA features. support Support |
6 | Will Entire JPQL Supported by ObjectDb? supported yet by ObjectDB. The main missing feature is subqueries. You may browse the issue tracking |
6 | ObjectDB Enhancer Tool in Java 9) yet. support Support ObjectDB 2.7.2 update did indeed solve issue 2) above. (Thanks!) I will consider this posting closed and instead track issue 1197. CBE CBE |
6 | Should I use ObjectDB and JDO? most of JDO 2.1 (except sub queries and a few other features, as you can see in the issue tracking |
6 | SectionClassifier message in logI'm trying to track down an issue in an application - the problem occurs around the retrieval of an object from a database the specifics are unclear at the moment. In the objectdb log the following message is written everytime the issue occurs. Could you give more detail about what this message |
6 | javax.transaction.Synchronization with Java SE 10.0.1 to track down why it is not found via runtime and discovered that within the method jdk.internal |
6 | config optimizing" /> <dirty-tracking arrays="true" /> </entities> <schema> </schema> <server> <connection port="6136" max="100 |
1 | ObjectDB 2.7.6 (no enhancement) by minimising tracking backups. Improved concurrency by using lock free Synchronization (issue |
