4 | Optimistic locking: prevent version increment on entity collection attribute Your test passes after fixing the relationship on the Document side to: @OneToMany(mappedBy="document ... of the collection fixed the issue! thank you very much for your great help. farid oudjanef Farid Oudjane Hello, I ... default to mapped by relationships. Please try build 2.5.0_05 that should fix it. support Support I will try that. Thanks Farid oudjanef Farid Oudjane |
4 | Objectdb Doctor should be used to fix the application. To fix broken references (i.e. to replace broken references ... fixing the application but it is an easy way to repair a specific database. support Support great |
4 | Soft Reference Object Cache Recommendation necessary (e.g. for dirty objects until commit). On the other hand the data store page cache is fixed ... on to memory when it should be freed? We are always open to check possible faults and fix ... that may be created. I also understand that those PAGs are fixed and ObjectDB will not free them. I also understand |
4 | Database corrupted after schema change to me that it is some failing schema evolution. When I tried to fix the DB file, the Doctor deleted ... #2621) that was fixed in version 2.8.4. Please try to open the database (maybe the version before ... with already corrupted data (by the schema change, without fixing the DB file with Doctor) using ObjectDB 2.8.5 |
4 | OneToMany and cascade delete problem are removed from the cache and then retrieved again, fixing the broken relationship). When using a short ... side can cause this strange behavior. Notice that this can be fixed by forcing retrieval of the mapped by ... ); em.refresh(p); // <= fixes incomplete bidirectional relationships em.remove(p); em.getTransaction().commit(); support Support |
4 | Problem with byte arrays in JDO - ClassCastException build 2.7.1_08. support Support build 2.7.1_08 does not fix the problem. sjzlondon Steve Zara You are right, sorry. It fixed a simplified test case but not your exact test case. Build 2.7.1_09 should fix your test case as well. support Support That did it! Thanks for your fast response. sjzlondon Steve Zara |
0 | [ObjectDB 2.6.7_04] Unexpected exception (Error 990)_04 or other recent builds, but to issue #1818, that was already fixed. It is unclear why the previous fix is not working, but build 2.6.7_05 includes some addition that maybe can help. support Support 2.6.7_05 works correct. Thank you for the fix. btc_es BTC EmbeddedSystems |
0 | Unexpected exception (Error 990) com.objectdb.o.InternalException should fix this exception, but only for this specific scenario as demonstrated by the test case ... collection. Build 2.6.1_02 should fix this issue. If the exceptions in your application ... well with the new build. support Support Thank You. 2.6.1_02 fix our problem. Now come no more errors. btc_es BTC EmbeddedSystems |
0 | Can't open replicated database Szurgot Yes, this should be fixed in one of the next builds. support Support Any idea when this will be fixed? bensteele Ben Steele No immediate fix is currently planned. The workaround is to make |
0 | Remove of an entry from a @OneToMany collection is not possible if the enhancer is disabled class MyEntity { int x; } } Build 2.6.0_04 includes a fix of this issue. support Support Hello, I have tried version 2.6.0_04. The problem with the @OneToMany collection is still not fixed. 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 |
