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 | ObjectDB Enincompatible with Quarkus?-timeout="0" /> <url-history size="50" user="true" password="true" /> <log path="$objectdb ... /" retain="900" /> <logger name="*" level="trace" /> </general> <database> <size |
6 | OneToMany and cascade delete problem: Store: 4, size: 10 Offer: Offer for product: 94, store: 4 Offer: Offer for product: 54, store: 4 ... test with enhancement enabled produces: Store: 4, size: 9 Offer: Offer for product: 64, store: 4 |
6 | Failed to read the value of field using reflection.ArrayList.size(Unknown Source) Player.toSFSObject(Player.java:45) <-- this is my code from here. I am trying to access the size of a List of an object I fetched from the database. ... The database |
6 | locks on pure query activities" /> <url-history size="50" user="true" password="true" /> <log path="$objectdb/log/" max="8mb" stdout ... name="*" level="info" /> </general> <database> <size initial="256kb" resize="256kb" page="2kb |
1 | ArrayIndexOutOfBoundsException: -1). You cannot disable that cache since it has a minimum size even if you request zero size. In some |
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 | ObjectDB 2.7.0Extended maximum supported entity object size to nearly 2GB. Added a temporary system property to disable "enhancement ... is old" checks. Fixed a bug in handling remove and persist of the same ... sizes larger than 64KB (which are not supported by ObjectDB). Fixed an issue of very slow online backup. |
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 | Sort of very large objects - out of memory creation time and priority The message size should be around 1mb so I think there should be around 11mb ... section is below for reference. <database> <size initial="256kb" resize="256kb" page="2kb |
