About Doctor

61-70 of 162Refresh
Forum
2

Left join fetch behaviour doesn't retrieve children?

with doctor", have you an other manner to check without doctor ( work bad with my database ) ? 4 ... optimization causes this in a specified case. 2- Using the Doctor. You can also run it in repair mode
Forum
2

Mismatch client-server protocol prefix

like very ordinary code. Could you check the database with the ObjectDB Doctor? I found some ... ObjectDB. In addition to checking the database file with ObjectDB Doctor, could you please check ... the Doctor. It found no errors. We use this method for over 3 years now. It's from the early days
Issue
2

Negative snapshot user count exception

.  I re-ran the database doctor on Monday evening PDT (circa 9/10 @02:40 UTC).   After restarting ... that cannot be fixed by the Doctor (due to the OutOfMemoryError, the upgrade, or any other cause ... the log after that restart, so hopefully the Doctor fixed these index issues. In that case
Issue
2

NullpointerException at a normal select

time, I've also tried to run the DB doctor with the following result: heintz@heintzmbp /usr/local/objectdb-2.5.6_02/bin> java -cp objectdb.jar com.objectdb.Doctor ../db/my_database_file.odb ObjectDB Doctor [version 2.5.6_02] Copyright (c) 2014, ObjectDB Software. All rights reserved. Scanning
Forum
2

Object Relations Error after Schema Change

. Could you please check the database with the ObjectDB Doctor and post the output? In addition, you can try migrating the data to a new database automatically by running the Doctor in repair mode. If this doesn't help ... the problem and suggest a fix. Hi,  we tried reparing the database with Doctor, tried changing the names
Forum
2

ObjectDB version 2.2 has been released

non optional field validation (throwing an exception on null value). Improved ObjectDB Doctor ... several bugs in query processing and running. It is highly recommended to run the ObjectDB Doctor of version 2.2 in repair mode on existing database files, and to switch to the new database files that are generated by the Doctor when moving to version 2.2.
Issue
2

Referential Integrity

. During development and testing it is recommended to use the ObjectDB Doctor to verify that reference integrity ... above, reference integrity can be checked by the ObjectDB Doctor (offline). Eventually standard ...  dangling references (and that can be checked with the Doctor), avoiding reference integrity checks
Forum
2

drop a column from table

fields), and of course commit the transaction. Alternatively, you run the Doctor in repair mode to create a new database file. The schema change must be available to the Doctor, so you must open the database after the schema change in your application to register the change, or run the Doctor with a classpath that contains your entity classes. Bimal
Result
1

ObjectDB version 2.2.8

in running online backup with no arguments. Added option for running the Doctor without activating disabled indexes. Fixed a Doctor bug in fixing old (< 2.0) database files. Fixed a temporary file
Result
1

ObjectDB version 2.4.1

Version 2.4.1 Fixed a bug of duplicating new objects during merge. Fixed a username/password issue in using EntityManagerFactory's getMetamodel. Fixed a bug in detachment of hollow objects on close (issue #799). Fixed a Doctor exception (issue #796). Fixed a Doctor bug in checking byte[] arrays