4 | Broken @ManyToOne reference.CHILD_ID is only part of the primary key now. support Support Hi support, just tried the fixed ... Vladimir Tsichevski Point 2 is indeed a bug. Build 2.4.7_09 fixes it. Regarding point 1, this is not ... . Please try build 2.4.7_10. support Support Hi support, thank you for fixing previous problems |
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 | Possible Bug in MEMBER OF the WHERE clause. Build 2.3.3_01 provides a temporary fix that makes your query work. Still SIZE and IS EMPTY are not supported yet and this should be fixed in future versions. support Support Thanks for the fix. Now it works. I hope you add comprehensive support for inverse collection fields in |
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 | like operator (String). You are right, LIKE with no wildcards should function as =. Build 2.4.7_17 fixes this behavior. support Support Thanks for the quick fix. This new version 2.4.7_17 fixes this issue. pezifromvienna Peter Sauer |
4 | Problem on JPA Merge Entity. and the useful test application. Please try version 2.0.5 that fixes the problem. support Support Thank ... try the version 2.0.5 and that don't fix the issue. I try it with the test application and my full application. In both case the bug is still there. Do you check if the new version fixes the problem |
0 | Error during closing an entity manager.e. if we release a build with an attempt to fix it would you be able to check it? support Support ... be your priority now. support Support We have found the reason of the optimistic lock exception and we fixed it in our code. From my sight of view this issue is fixed. btc_es BTC EmbeddedSystems |
0 | TYE NullPointerException I think it will go away when I fix something in the test itself but I ... . Build 2.3.1_03 should fix the exception (but notice that the data will not be available ... - a better fix is included now in build 2.3.2_01. Lazy collections will always hold a strong |
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 | ObjectDB 2.5.3Added support for casting from boolean to int in queries. Changed default value of <exclude-unlisted-classes />. Fixed a critical Explorer bug that interferes with queries on enum fields. Fixed a multithreading conflict (missing synchronization) in the JPA metamodel API. Fixed implementation of casting (as) in criteria queries. |
