6 | Size of recording directory keeps growing the configuration file. If it is "all" you can save a lot of space (and improve performance) by switching |
6 | TimeSeries and ObjectDB. This could be efficient it terms of space and retrieval speed but may be more expansive in updates |
6 | UserException - Object User#2 belongs to another EntityManager (which is forbidden, since every EntityManager manages its own space of managed objects, and a managed object |
6 | ObjectDB version 2.2 has been released to handle additional issues. Improved query execution planner. Improved cleanup and reusing space |
6 | @MappedSuperclass and @Transient not working as I expected entity classes) do not store data just schema. Usually data in ObjectDB consumes much less space than the same data in a JPA/RDBMS combination. support Support |
6 | OutOfMemoryError on search after update on DB created with DB Doctor.OutOfMemoryError: Java heap space at java.util.Arrays.copyOfRange(Arrays.java:2694 |
6 | significant performance decrease"> <quota directories="5" files="20" disk-space="5mb" /> </dir> </user> <user username="user1 |
6 | First persist takes long time storage space, etc.) so this is expected. If you are concerned because you have to repeat |
6 | OutofMemory error with Object DB 2.0,delete"> <quota directories="5" files="20" disk-space="5mb" /> </dir> </user> <user |
1 | ObjectDB 2.2.0 and reusing space after index deletion. Changed default configuration (enabled recovery, disabled |
