7 | Connection is closed Caused by: java.io.EOFException" /> <cascade-persist always="auto" on-persist="false" on-commit="true" /> <dirty-tracking arrays |
7 | significant performance decrease="false" /> <cascade-persist always="auto" on-persist="false" on-commit="true" /> <dirty |
7 | Schema migration - long to String a workaround you can read and write (after making them dirty) all the instances of that modified type |
7 | Remove a modified entity cause an optimistic lock exception). Can you explain the optimistic lock exception? It seems that the first level cache contains yet a dirty entity |
7 | The server cannot start in CentOS-persist always="auto" on-persist="true" on-commit="true" /> <dirty-tracking arrays="false |
7 | ObjectDB Enincompatible with Quarkus?" on-commit="true" /> <dirty-tracking arrays="false" /> </entities> <schema> </schema |
7 | Degrading performance overtime-persist always="auto" on-persist="false" on-commit="true" /> <dirty-tracking arrays="false |
7 | locks on pure query activities="false" on-commit="true" /> <dirty-tracking arrays="true" /> </entities> <schema> </schema |
1 | each 1-2 days objects on some objectdb level lock/block each other" /> <dirty-tracking arrays="true" /> </entities> <schema> </schema |
1 | Best practise loading big data to hold strong references (which prevents garbage collection) to non dirty entity objects |
