6 | Access entity version before commit transaction ObjectDB seems to automatically update the version since it returns 3 here }); Hint |
6 | Is there any restriction when using fetch=FetchType.LAZY ? (although it is only a hint in JPA and ObjectDB is allowed to ignore it and load data eagerly). On detach some |
6 | Issue with Casting / Joins, maybe this can be solved by adding a new ObjectDB specific hint. support Support hi, okay, asked |
6 | JPA and handling large data sets the way is slow. We have an own entity for storing binary data (pictures, documents). Hint |
6 | Unexpected internal exception during set field of an Embeddable to null and debugging I hope that I found a important hint. The stack trace has been reduced to very (by the printer |
6 | performance limit the objectdb.result-fetch query's hint in order to separate query execution from result loading. Loading |
6 | Enhancement Check instanceof com.objectdb.spi.SignedType support Support Hello, thank you for the hint, it performs |
1 | NullPointerException: Cannot invoke "com.objectdb.o.RFV.S()" because "<local9>" is null for the hint with the query. I used the correct query in the code above but the exceptions is still thrown |
1 | Unexpected Exception during commitI'm testing code that otherwise has been working with a clean database. I have seen several examples of the following exception. It never seems to happen in the same place twice, though. If you can give me a hint as to what would internally cause this, I'll try to reproduce it. Carl [ObjectDB 2.2 |
1 | Lazy loading of mapped by (inverse) singular referencesObjectDB ignores lazy setting of non collection mapped by (inverse) fields and loads them always eagerly. This is allowed by JPA since lazy is only hint but it is not efficient. The reason is that currently when an entity object is loaded all the referenced objects are instantiated immediately |
