5 | @Unique member combination not working is implemented as an index), and therefore requires index rebuilding (currently using the ObjectDB Doctor). support Support |
5 | Saving custom list which implements java.util.List fails), and check the database with the ObjectDB Doctor. But please do that in a separate thread in the issue |
5 | Automatic schema evolution causes ArrayOutOfBoundsException. The objectdb doctor states "No errors have been found". Is there any other way to resolve this schema update |
5 | JPA-Query does not lead to any result"). If you have more information about this specific file it may help. You should be able to fix indexes by running the ObjectDB Doctor. support Support |
1 | Internal objectdb exception when using different language on a machine reference to a type id that doesn't exist. Could you please check the database file with the Doctor |
1 | InternalException the database with the Doctor and post the output? support Support This issue is closed |
1 | Why is ObjectDb is holding onto classes that no longer exist? but when the Doctor is run, and can be ignored. support Support Cool! Thanks a million for the reassurance |
1 | ObjectDB 2.7.6Added support of an option to disable broken reference cleaning in the Doctor (feature request #2341). Added support of cascading delete using JDO (feature request #2329). Added logging for "Failed to read from file" error (issue #2322). Added an option for eager background purge of weak references |
1 | Internal error this exception - close persistence and run the Doctor? Ignore it and try again? The product |
1 | ObjectDB 2.7.3 queries. Fixed a bug in schema evolution of indexes. Fixed a new false alarm of the Doctor, since 2 |
