Internal Website Search

91-100 of 200 resultsRefresh

Possible cause for "Enhancement of type ... is old and cannot be used"

= GenerationType.TABLE (www.objectdb.com/ticket/1823) You had attempted to fix it in ... " when using a TableGenerator. That problem was demonstrated by the provided test case, fixed ... > webel Dr Darren Kelly The bug was found and fixed in build 2.6.9_01. It can affect any

Java 8 Enhancer Problem

you for this report. Please check if  build 2.5.5_01 fixes this issue. support Support Build 2.5.5_01 fixes this issue but it has a new bug. When I fetch, detach, change and merge ... to the Enhancer fix, but to another fix (issue #1373). Please try

Problem with distinct select, order by and equivalent alias/attribute path

could this be fixed? Is the last (problematic) query invalid from your point of view? Thanks ... expressions that are also logically wrong. support Support Confirmed this fix ... (that actually differ from the queried root entity). I will post a thread there to see if someone can fix

Unable to convert 1.x odb file to 2.x

to fix them. support Support Thanks for the fix. It helped for the above mistakes ... of objects as the value in the HashMap. Can this be fixed too?  jakab Gergely Jakab This map issue would be much more difficult to fix, since no exception with a stack trace

Doctor fails to run when running in parallel on more DB files.

.Doctor file1.odb fixed/file1.odb&\ java -Xmx100G -Djava.io.tmpdir=$tmpdir -cp objectdb.jar com.objectdb.Doctor file2.odb fixed/file2.odb&\ java -Xmx100G -Djava.io.tmpdir=$tmpdir -cp objectdb.jar com.objectdb.Doctor file3.odb fixed/file3.odb&\ java -Xmx100G -Djava.io.tmpdir=$tmpdir -cp

ClassCastException during query

move the enum class into the entity package, this has organization reasons. And I tested your fix with the last ObjectDB patch 2.7.6_02, but the fix does not work. We got the same exception as ... tested your fix with the last ObjectDB patch 2.7.6_02, but the fix does not work. Changes in

ObjectDB 2.8.9

">issue #2817). Fixed the error message when required enhancement is missing (issue #2828). Fixed recording of large transactions over 2GB in size (issue #2834). Fixed a bug in executing compound range

JDO PersistenceManager.getSequence() returns null sometimes

our large existing JDO 1.2 codebase. spiffy Jonathan Harley Build 2.4.7_04 fixes this problem ... > This could be easily fixed if this is how it works in other JDO implementations. support Support Confirmed that 2.4.7_04 fixes the problem - thanks! Yes, I expect

ObjectDB 2.2.3

> Added Maven build 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

ClassCastException thrown when running count query

could fix ObjectDB to return correct results for the second query (even though there are broken ... a new build with the fix will be produced. support Support The orphan Position records ... . It's really fast. mosi0815 Ralph Moser Please try build 2.3.1_04 that should fix