About fix

81-90 of 200Refresh
Forum
1

"Attempt to lock a non entity object" error

) Is this enough information for someone to suggest what might be happening and how to fix it? public void doEdit ... above setRestoreValues was replaced with setRetainValues (it is fixed now). Sorry for the error ... also works with the fix. The new behavior and your quick fix are greatly appreciated. AlphaOne
Result
1

ObjectDB version 2.0.2

Version 2.0.2 Fixed a bug in queries on embedded objects in C/S mode. Fixed a bug in setting log directory path (missing URL decoding). Fixed a bug in automatic byte code enhancement in Java EE server. Fixed a bug in multi variable queries.
Result
1

ObjectDB version 2.1.0

to NonTransactionalWrite enabled (issue #142). Fixed a bug in distinct queries (duplicates due to bad optimization). Fixed a bug in viewing TreeSet and TreeMap in the Explorer. Fixed detachment of entities by replacing proxy objects with ordinary objects. Fixed a schema evolution bug when adding a new super entity class.
Result
1

ObjectDB version 2.2.1

Version 2.2.1 Added support for using ObjectDB with JBoss AS 6.0 / 6.1. Fixed several bugs in handling eager fetch. Fixed a pessimistic locking bug. Fixed a bug in using primary key fields in queries. Fixed a bug in queries on deleted objects before commit / flush.
Result
1

ObjectDB version 2.2.3

enhancement to the bundled examples. Fixed a schema evolution bug in renaming user types. Fixed a bug in handling schema evolution (regression of 2.2.0). Fixed a bug in queries on large objects. Fixed a bug
Result
1

ObjectDB version 2.4.4

notification feedback. Fixed a bug in filtering mapped by objects by type. Fixed a regression bug in using primary key fields in queries. Fixed a regression bug of duplicating new objects on merge. Fixed a Doctor bug that caused false alarms.
Result
1

ObjectDB version 2.4.7

Version 2.4.7 Fixed bugs in cascading merge and refresh. Fixed an internal java.lang.ArrayStoreException bug (com.objectdb.o.InvToOneLoadRequest). Fixed a regression bug (starting 2.4.4_13) in handling embeddable types. Fixed a performance regression (since 2.4.4_01) in query result retrieval
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
Issue
1

[ObjectDB 2.6.9] Unexpected exception (Error 990)

. - has 142351616 entries instead of 142351618 Try to run the Doctor to fix the production database. Do you still get the exception in production after fixing the database? In production it takes about 18 hours, and finish ok! This report is similar to the report in issue #1977  that was fixed
Forum
1

c.o.jpa.type.EntityTypeImpl.getIdType() returns null

only for ID classes and not for simple single field IDs. Version 2.2.3_01 should fix this. Thank ... you with more code/xml or an sample project You should use 2.2.3_01 (the fix was applied ... have deployed the 2.2.3_01 version to my mvn repo and this fixed the problem. thank