7 | First query takes 4+ minutes to complete="info" /> </general> <database> <size initial="1024mb" resize="256mb" page="2kb" /> <recovery |
7 | Wrong select results> <size initial="1024kb" resize="1024kb" page="64kb" /> <recovery enabled="true" sync="false" path |
7 | odb file size doesn't shrinkHello, why delete from ... doesnt modify size of odb? Even in in embedded mode, and in server mode i use recovery, not recording mode. mastervoland Vladimir Sadovnikov When objects are deleted from the database their space is marked as unused and becomes available for future objects. The size |
7 | config optimizing" /> </general> <database> <size initial="256kb" resize="256kb" page="2kb" /> <recovery enabled="true" sync="true |
7 | unable to update table in slave server database" /> <recovery enabled="true" sync="true" path="." max="128mb" /> <recording enabled="true" sync="true |
7 | locks on pure query activities" /> <recovery enabled="true" sync="false" path="." max="128mb" /> <recording enabled="false |
7 | Performance tuning, best practices="256kb" page="2kb" /> <recovery enabled="true" sync="false" path="." max="128mb" /> <recording enabled |
1 | Unexpected Exception (Error 990) with ArrayIndexOutOfBoundsException, discarding the recovery file of a database, etc. but it would be impossible to know |
1 | ObjectDB 2.0.0 a bug in the new log based (recording) recovery from failure mechanism. Fixed a bug in finding |
1 | javax.jdo.JDONullIdentityException: The identity must not be null. playing together? Is it some kind of cache? lorenz2304 Benjamin Lorenz The $ file is the recovery file. support Support |
