6 | Server connection management Side) You should be able to set the connection pool size by a property in persistence.xml: <properties ... size is 50. support Support This is very useful information. I do, however, get the exception reported |
6 | ObjectDB Clustering VS Hadoop Hbase, the ObjectDB clustering can not support a database whose size is beyond the size of the master node |
6 | Merge with Parent/Child entities not possible.assertEquals(4, parentEntity.getChildren().size()); entityManager.getTransaction().begin ... .refresh(parentEntity); Assert.assertEquals(1, parentEntity.getChildren().size()); } } wua Andreas |
6 | Embedded in JDO metadata not working in objectDB 2.x ?. So my questions are: 1. Is the enormous increase of database file size caused by the number of not ... . Is the enormous increase of database file size caused by the number of not-embedded objects in ObjectDB 2 |
6 | Bulk Delete and Update - best practice? transactions are limited to the heap size, so this test that deletes and updates more than 500MB of data in one transaction requires a larger heap size. This limitation may be removed in future releases |
6 | Query filter comparing DatesHi, I am using an indexed java.util.Date field in my Entity and I came across some weird behaviour in query filters comparing this Date field. Could You please clarify why are there zero-size result collections in the first pack of queries and non-zero size results in the second pack ? I |
1 | I can't get cascading delete to work in JDO>)query.execute(); System.out.println("Holders: " + holders.size()); query.closeAll ... <Dependent>)query.execute(); System.out.println("Dependents: " + dependents.size |
1 | cannot delete objects after crash (see issue 2283)after the crash we cannot delete specific objects, see screenshots of explorer. Database will be soon available (size 5.561.119 KB) on hummingbird-systems.com, user/pw your db name, main menu option ... (size 5.589.297 KB). upload is complete we are meanwhile in a problematic situation at that customer as |
1 | out of memory error space). Increasing the JVM heap size could solve the problem, or alternatively, tuning ObjectDB configuration to use less heap size. If the exception is thrown in embedded mode you may wrap relevant |
1 | database corrupt" /> <url-history size="50" user="true" password="true" /> <log path="$objectdb/log/" max="8mb" stdout ... ="*" level="info" /> </general> <database> <size initial="256kb" resize="256kb" page="2kb" /> <recovery |
