12 | 500Mb ObjectDb database opening issue500Mb ObjectDb database opening issue |
12 | pm.newObjectIdInstance returns nullI am on an emergency upgrade mission. Our production odb file (version 1.0.4) currently corrupts when written to. Importing to 2.6.8. has seemed to fix the corruption problem. So....I am in the middle of testing a 2.6.8 upgrade from 104se_2522. It was plugged in to the existing legacy code (2005 |
12 | How to enable and disable auto schema update?(my specified entity libs) then the whole db is being corrupted and db need to be restart. Expected : Instate of updating the schema with old library db should throw some error and data should not corrupt. Thank |
12 | ODB should auto-restart if it detects it's necessary. Moreover, this would considerably reduce the chances of corrupting the database. (A problem that I've suddenly encountered in ... . Therefore, I would really appreciate this new feature in ObjectDB, which would definitely avoid corruption |
12 | Consequence of lost ODB$ Files? was written to it) it is possible that your copy will be a corrupted database due to inconsistent file ... Doctor, and if necessary, use the Doctor to repair any corrupted database files. support Support |
12 | Removing an entity throws exception was corrupted, because when I tried to create new project as a test case for this bug, with new ... demonstrates cannot cause a corrupted database. The problem was the result of comparing object images (used |
12 | Reading 1.x odb files in ObjectDB 2.x without upgrading one odb file. The new odb file is corrupted. I am attaching both new and old odb file. And i am doing ... [] {oldOdbFileName, newOdbFileName}); I always gets corrupted database. I am doing coversion of 6 |
8 | Error using query with MAX() function) may cause database corruption, so it is highly recommended to use the new build. support Support |
2 | javax.jdo.JDONullIdentityException: The identity must not be null. Benjamin Lorenz After this crash, the database seems to be corrupted, I cannot execute my pages ... during close) and not a corrupted database. Anyway, please try build 2.4.0_03 that should fix this issue |
2 | NullPointer on query Richard Szurgot The database file is corrupted. A post mortem analysis reveals that the last change ... it's possible that the db file corruption may be unrelated and occured when the process was shutdown |
