Home » Search

About fix

1-10 of 200Refresh
Manual
61

Database Doctor

Explains how to use the ObjectDB object database Doctor tool to diagnose and repair database files and damaged Java/JPA/JDO objects.
Manual
10

Database Management Settings

, the recovery file can be used to fix the database. Recovery from failure is automatically applied by ... . When recording is enabled and recovery is disabled, recorded operations are used to automatically fix
Result
7

Posting to ObjectDB Website - Important Instructions

,  ArrayIndexOfBoundsException, etc, which obviously require a fix (at least an improved error message) should be posted
Manual
7

JPA Persistable Types

must be fixed, since changing a name can cause data loss in existing databases. The @Enumerated
Result
3

ObjectDB version 2.4.0

on detachment to null (rather thanempty collections). Fixed a critical bug in handling a very large number of entity classes (issue #672). Fixed LockModeType.OPTIMISTIC (READ) by handling it as OPTIMISTIC_FORCE_INCREMENT. Fixed a bug in optimistic locking on find by using LockModeType.WRITE. Fixed
Result
3

ObjectDB version 2.0.0

for class loading and method finding problems. Fixed a bug in the results of IS [NOT] NULL queries. Fixed a bug in ObjectDB Doctor. Fixed persistence.xml C/S connection property to "javax.persistence.jdbc.user". Fixed a bug in the new log based (recording) recovery from failure mechanism. Fixed a bug in
Issue
3

again merger missing logs + objectdb exception

morning Hopefully you will be able to fix the database with the Doctor before restarting the server ... . Meanwhile, have you fixed the database using the Doctor and started the system again successfully ... to the database corruption. For this we probably have meanwhile a fix. As regards the query, we'll try to find
Result
2

ObjectDB version 2.2.9

file suffixes. Changed fetch of collection elements. Fixed a bug in query plans that use an inherited index. Fixed an ArrayIndexOutOfBoundsException bug in using nested embedded objects. (issue #415). Fixed a JMX Remote - ObjectDB Enhancer Agent conflict. Fixed a ClassCastException bug in complex JOIN
Result
2

ObjectDB version 2.7.0

system property to disable "enhancement ... is old" checks. Fixed a bug in handling remove and persist of the same object in one transaction (issue #2027). Fixed objectdb.jar to include META-INF/MANIFEST.MF as the first entry (required by Apache Karaf). Fixed a cache bug in repeating some sorts of LIKE
Result
2

ObjectDB version 2.5.6

Version 2.5.6 Changed merge behavior (following this forum thread).  Fixed a TomEE - ObjectDB client-server integration issue (issue #1407). Fixed a ClassCastException on selecting an embedded ID field in queries. Fixed an exception (NullPointerException) in update queries (since 2.5.5_12). Fixed