Home » Search

About corrupted

31-40 of 61Refresh
Forum
2

Removing an entity throws exception

you for fast response. The fix changed the number 51 to 34. But it looks like my db was corrupted ... a corrupted database. The problem was the result of comparing object images (used mainly to detected changes
Result
1

ObjectDB version 2.3.7

Version 2.3.7 Fixed a critical issue that may cause database corruption (issue #630). Initial attempt to enable navigation through lazy loading from detached objects (feature request #326). Improved toString of criteria queries to use aliases (issue #127). Fixed automatic variable naming in
Result
1

ObjectDB version 2.7.1

Version 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
Forum
1

@JoinColumn(nullable=false)

During the evaluation of ObjectDB (We're currently developing with EclipseLink/mysql) I noticed was the following: I marked a @Column as nullable=false Than I tried to save it with the property as null It worked, without any problem, now I have a corrupt dataset. I expected an exception or
Issue
1

[ObjectDB 2.6.9] Unexpected exception (Error 990)

) may cause database corruption, so it is highly recommended to use the new build. jastorga
Issue
1

ArrayIndexOutOfBoundsException: -1

pages. Therefore it could corrupt the database, as demonstrated by your test. Consequently many types
Forum
1

ClassCastException on SELECT NEW ... after UPDATE over Java RMI

after the query is in trvr-corrupt.zip. As you can see the update completes Ok. We see the problem
Issue
1

com.objectdb.o.InternalException: java.lang.ArrayIndexOutOfBoundsException: null:

bug that could corrupt databases when the total number of entity classes, indexes, and sequences
Issue
1

EOFException

if it will be of much use to you. The database file that you uploaded is corrupted and you must repair
Forum
1

Error using query with MAX() function

) may cause database corruption, so it is highly recommended to use the new build.