Home » Search

About build

81-90 of 200Refresh
Issue
1

ClassCastException thrown when running count query

. Regards Ralph Moser The exception is in code that was modified in the last build 2.3.1_03. Although I don't see how the change is relevant - you may want to try running your test with build 2.3.1 ... a new build with the fix will be produced. The orphan Position records are there because i deleted some
Forum
1

Date field Index is corrupted due to time change

move during commit different values can be obtained for the same field. Hopefully a new build that fixes this bug will be released soon. Thank you very much for this report. Build 2.6.4_02 should fix this issue. Thank you for making a build that contains the fix available. We will test
Forum
1

deadlock with newest version 2.4.4_16

. if you could advise that would be great. Dan   Thank you for this report. Build 2.4.4_17 should fix this deadlock ... to do so or not. A synchronized that was added in build 2.4.4_10 to fix another problem caused the deadlock. All builds pass the same tests before release, but that deadlock was not detected. Before
Forum
1

Eclipse4 RCP - No Persistence provider for EntityManager

since build 2.6.2_02. You can still use objectdb.jar with JPA bundled in the same JAR also after build 2.6.2 ... loader works only this way (i.e. between building an EntityManagerFactory to building
Forum
1

EntityManager JPA or JDO impl and different behavior

. import the test project to eclipse 3. In eclipse, change your java build path to remove the M2_REPO ... everything is running on c drive.   Thanks, Eitan Build 2.3.4_04 should fix the new "Failed to write to file ... m2eclipse and then replacing the jar with dependency on the ObjectDB project didn't work. Please try build 2
Issue
1

Error during closing an entity manager

the same class hierarchy is not supported. But we have done a full clean and build of our entity ... that case it is a bug. Do you have a way to reproduce it? i.e. if we release a build with an attempt ... .1_02, but the error throws again. Could you please check build 2.7.1_03? I have a further hint
Forum
1

Error using query with MAX() function

processing large objects in queries. Please try build 2.2.2_02 that should fix this issue. Thank ... .java:30)   Apparently the previous fix was incomplete. Please try the new build (2.2.2_03). 2.2 ... ) it might help in understanding the problem. If you are using EntityManager's flush you should try build 2.2
Issue
1

Error whilst running

. It seems that a change between builds 2.4.4_10 to 2.4.4_17 causes this error, but probably only in ... ). Build 2.7.2_01 should fix this bug. Build 2.7.2_01 has a side effect that introduces another bug (issue #2142). Build 2.7.2_02 should be used. CalculationServices
Issue
1

Exception upon index definition change

in this case. If you can share a test case that throws the exception it would help. Please try build ... Markus Unfortunately we had to revert the changes in build of 2.7.2_03 in build 2.7.2_04 as ... will be provided soon. Please try build 2.7.2_05, which should fix the issue again. doppelrittberger
Forum
1

Getting java.lang.ArithmeticException: / by zero

the stack trace if you provide the exact build number that you use (or upload the ObjectDB jar file). Please find the attached object db jar. I couldn't find the build number. It may be a very old jar. Please try the attached jar, which is the last build of ObjectDB 1.x embedded. Hi, Thanks