Internal Website Search
191-200 of 200 resultsRefreshMerge of entity classes with "mapped by" very slow objects that are already managed should be very fast. Build 2.4.2_02 fixes it. support Support Thanks for new build. Fix is working correctly. The speed ... . Hopefully most of the performance gain will remain also with the new fix. support Support | |
Possible issue with String fields build 2.3.7_16 that should fix it. If it doesn't - please try build 2.3.7_13. fix, it would be better if possible to avoid temporary file (to improve efficiency), e.g. by ... > That fixed it.. Have now split transactions into batches of 1000 recs .... 370,000 | |
Can I Disable the Creation of the "log" Directory? report in the Issue Tracking system)? CBE CBE Build 2.6.8_07 should fix this issue. Thank you for the report. support Support Confirmed. The fix works for me. Thanks! CBE CBE | |
Database is erased after deploying a new web application version that if I'll back up the .odb file, delete it and then restore it will fix the issue of accessing ... the queries. It looks like the problem is fixed when I close the entityManagerFactory | |
Duplicate Entity class names causes Exception in Query will try to run your test. support Support Build 2.2.9_05 includes an attempt to fix the NullPointerException. The fix is based on the stack trace | |
Weird issue with variable naming I was trying to replicate it which is similiar to what we do. We'd really need this fixed urgently ... after debugging!! thanks for a fast fix, Alex quasado Alexander Adam Yes, toString invocation should not affect. Build 2.3.6_08 fixes it. support Support | |
Unexpected Query Token / Casting in Query Adam I fixed some issue in ObjectDB in navigation after casting. Then I had to add ... ). I fixed it. But the navigation from the collection (bankAccounts ... so is there a fixed version available yet? thanks a lot! Alex quasado | |
Online Backup degrades responsiveness. completely fixes the issue and I'm not sure how scalable this and costly it would be as the DB gets ... ;actually fixes original errors. Trianglehead Json Error This has been confirmed to fix | |
Inefficient memory usage with very large transactions analysis (see #9 in this forum thread), and was fixed in build 2.4.3_02, but the fix was removed later in build 2.4.3_03 because it caused other problems (#10, #11 in that forum thread). support Support Version 2.4.4 fixes this issue | |
Deadlock on Schema Update during Multithreading activity A possible deadlock was detected when new types are registered during multithreading activity against ObjectDB. Until this issue is fixed ... . support Support Version 2.5.1 should fix this issue. support Support |