ObjectDB Database Search

51-56 of 56 results


	doctor error message after database getting page errors Here is a link for the corrupt database: https://www.dropbox.com/scl/fi/6ywgr9yx459c9tskv525t
	Failed to resize file - file system limitation error ". So it does seem as a specific system issue rather than a bug in ObjectDB or a corrupted database file
	objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check") vs. generic classes with interfaces: detailed investigation Clean and Build has not been corrupted . - No javaagent enhancement is used at any stage
	ODB lost? I'm new to ObjectDB. While debugging small programs in single-step mode in NetBeans, the ODB appears to get corrupted or lost if I don't invoke close on EntityManager. If I re-run my program and get a new EntityManager, the instance behaves as if the data that was persisting is somehow gone. I
	ObjectDB 2.7.1 Fixed a critical bug that may cause database corruption ( issue #1977 ). Improved error messages on entity operation exceptions. Fixed a NullPointerException on cascading persist throw an unloaded collection ( issue #2049 ). Fixed the location of a temporary file for index update ( issue
	EOFException The database file that you uploaded is corrupted and you must repair it using the ObjectDB Doctor before

doctor error message after database getting page errors