8 | Filename.odb$ Persisting Issue starting and stopping the program in quick succession or after running it for extended time ... Stage primaryStage; private static BorderPane rootLayout; @Override public void start(Stage |
7 | Query problem after transaction commit_Connection: connecting 02> Test_Connection: connected 03> UI: start query [query for all object Goods ... = % 06> UI: end query 07> UI: start printing result 08> code= A, desc= Good A, byUser= test 09> code ... 12> Goods creation: D created [create Goods D successfully] 13> UI: start query [query for all Goods |
7 | Database size is much larger than expected (x2) by starting from the failed program and removing unnecessary code until the problem remains ... - but don't expect a quick fix in this case. Please try build 2.2.9_04 that should improve byte[] persisting |
7 | Homepage and forum nearly inaccessible, since I started using ObjectDB. I'm also accessing from Europe, and many times I have up to 15 seconds ... . Thank you ObjectDB for your quick fix, which is what we all now expect from you, as normal |
7 | in-memory and on-disk support?I've had a quick read through the features/FAQ and haven't been able to find a clear answer. I'm looking at replacing a setup of H2 where I have 40GB in-memory backed by 800GB on-disk, the 40GB in ... - a very large cache (40GB) has not been tested yet. Starting with a 800GB database file seems as a good idea in |
7 | EntityManager JPA or JDO impl and different behavior we use spring to start everything. If I do: System.out.println("EntityManager Name: " + em.getClass ... eager fetch in this case. support Support Hi, Thanks for the quick investigation |
7 | Threading Problem (maybe with Criteria)Hi all I found some threading problems I do not understand: After creating some testobjects (i.e. 100000) the test opens the Database, start some queries with criteria in several threads (maybe 10 ... ). support Support Thank you for quick response Sorry I missed to remove this classes, the testcase (testcase |
1 | queries under 2.7.6_4 significantly slower than under 2.7.6, if you can identify the exact build in which these new issues started (_01, _02, _03 or _04) it could help ... that - if you need a quick solution), but we are working on a better solution that will solve the issue |
1 | queries more than 10 times slower using 2.8.1 versus 2.7.6 = 0 and o.state = 0) Therefore, the optimal query starts by using the composite index "ctso ... of ObjectDB. However, as a quick solution you can force ObjectDB to use the query plan that uses the index |
1 | javax.servlet.ServletException: Annotated methods must follow the JavaBeans naming convention. __odbHidden_getPropertyName 2.2.6_01 included a dirty and quick fix that used get as a prefix for both get and set persistent ... well. support Support Starting build 2.6.4_03 Enhancer generated hidden methods will have a __odbHidden_ prefix |
