7 | problem with lazy loading - unittest project attached not the best way to test it, it's more like an integration test. i try to test 4 requests in one test |
7 | Error with org.springframework.data.jpa.domain.AbstractPersistableI am working on a Spring Boot application. I want to integrate ObjectDB with Spring Data JPA. I refer to the http://www.objectdb.com/database/forum/860 to do the configuration. When I start up my application, I got below error. It seems like ObjectDB does not support a generic @ID in the super |
7 | ObjectDB stability after power failureI'm considering using ObjectDB in a system that is going to be running continuously without support instantly available for many years. How stable is ObjectDB when it comes to power failures and unattended restarts? Is database integrity maintained during such events? I have seen database vendors |
7 | Performance in SELECT statement why this query tooks so long. edit: I just tried to remove the second entity completely and integrate |
7 | Failed to commit transaction: Attempt to reuse an existing primary key value (613)I am using ObjectDB 2.8.3 version for my University Project which currently i am trying to inplement an Integration testing to one of my DataAccess methods. But, the problem comes before i try the method i want to be proved, exactly when i try to set up the database. These one is the test method |
7 | objectdb:2.8.4 & 2.6.1.b06 backward compatibility you if any issues will be observed during integration or testing! Harman Alexander Golyshkin |
7 | Issue with compile time enhancementI have an entity library which I have integrated build time enhancement in. The enhancer reports it has processed all of my persistent classes. When I attempt to run a Bootstrap process with this library I get the error shown below. The entity referenced in the error (Terms) is listed as having |
1 | Remove of an entry from a @OneToMany collection is not possible if the enhancer is disabled. wua Andreas Wurm You are right, sorry. Somehow the fix has not been integrated into that build. Please try build 2.6.1. support Support |
1 | ClassCastException thrown when running count query enforce reference integrity and it is the application responsibility to avoid deletion from the database |
1 | ObjectDB 2.5.6Changed merge behavior (following this forum thread). Fixed a TomEE - ObjectDB client-server integration issue (issue #1407). Fixed a ClassCastException on selecting an embedded ID field in queries. Fixed an exception (NullPointerException) in update queries (since 2.5.5_12). Fixed |
