Home » Search

About fix

131-140 of 200Refresh
Issue
1

Inefficient memory usage with very large transactions

this forum thread), and was fixed in build 2.4.3_02, but the fix was removed later in build 2.4.3_03 because it caused other problems (#10, #11 in that forum thread). Version 2.4.4 fixes this issue, hopefully without undesired side effects. lwalkowski
Issue
1

Internal exception on flush

multithreading issues that require fixes. Any test that you can post and will demonstrate ... and fixed using the test in issue #625. It is possible that this bug caused also the exception at #1 so this issue will be marked as fixed. felixobjectdb
Issue
1

Internal exception when quering

2.5.1. Could you provide us fix or some advice? If more info is needed, we can provide it. Thank ... , you are right. When do you plan to fix this issue? We would like to avoid checking for duplicities in every list of values in our selects:( Thanks Marta Build 2.7.2_01 should fix this bug (which is a duplicate
Forum
1

java.io.IOException: Illegal seek

more It seems to be issue #621 that was fixed - please switch to build 2.3.6_14. You may have to fix your database ... and checking the db file by Doctor. Maybe the Doctor cannot fix this specific issue. Try to use 2.3.6_14
Forum
1

JPQL keyword in entity - what to do?

as field names. Please try build 2.1.0_01 that should fix it. I did some tests and fix ... . Could you upload a test program that reproduces this issue?   Update: Build 2.1.0_03 fixes all these issues. lwalkowski
Forum
1

like operator (String)

with no wildcards should function as =. Build 2.4.7_17 fixes this behavior. Thanks for the quick fix. This new version 2.4.7_17 fixes this issue. pezifromvienna
Forum
1

Merge of entity classes with "mapped by" very slow

entity objects that are already managed should be very fast. Build 2.4.2_02 fixes it. If the problem ... for new build. Fix is working correctly. The speed boost is huge for some ... most of the performance gain will remain also with the new fix. lwalkowski
Forum
1

New to Product & Having An Issue

a while and forgot how those worked.  I fixed the test case to use @BeforeClass and @AfterClass and made the changes ... as expected.  The query tests still failed however. I think I found and fixed the bug. Thank ... was wrong (about comparison of embedded objects) - I just fixed it. By the way, equals should also work
Forum
1

Objectdb Doctor

identifying failures. If the Doctor reports broken references - the information should be used to fix the application. To fix broken references (i.e. to replace broken references with null values) in an existing database file you can run the Doctor in repair mode. This cannot replace fixing
Forum
1

OneToMany and cascade delete problem

the cache and then retrieved again, fixing the broken relationship). When using a short term ... this strange behavior. Notice that this can be fixed by forcing retrieval of the mapped by side, using ... (p); // <= fixes incomplete bidirectional relationships     em.remove(p);     em.getTransaction().commit(); lwalkowski