ObjectDB Database Search

stability issues have been fixed in version 2.9.3 and there are no new known issues. If you create ... procedure that depends on the MAC address of the device. This used to be fixed in the past  ... the newest version. I fixed it in the other ticket.   Kevin Kevin Pfaff No problem. Please see the reply in your private support ticket. support Support

Using version 2.7.4_01, we did a repair. After repair a former link to a missing reference was converted to null. This cannot be deleted using explorer   hgzwicker Hans-Georg Zwicker Thank you for this report. Build 2.7.4_02 fixes the issue. support Support

ObjectDB 2.3 has been released and it includes important additions and fixes : Added the ability ... #453 ). Completed missing documentation (e.g. UPDATE & DELETE queries). Fixed memory leak issues. Fixed server hang and deadlock issues. Fixed several NullPointerException bugs. Fixed the "Failed

before or after an attempt to fix it? Unfortunately it is possible that the database is corrupted in ... the fixed one, we can try fixing it, if the data is there. Note that there were no changes in ... our embedded system hgzpincher Hans-Georg Zwicker As it seems that the Doctor fixes the database

. That's all. I would really appreciate a fix for this, because it's holding back my team. Thanks ... is a feature that was added / fixed recently, and possibly has side effects, so you may want to avoid it. Unfortunately we cannot provide same day fixes for issues that are not demonstrated

ObjectDB 2.2 has been released and it includes important additions and fixes : Added full support ... after index deletion. Changed default configuration (enabled recovery, disabled recording). Fixed a critical database corruption bug ( issue #187 ). Fixed a critical bug in schema evolution

move during commit different values can be obtained for the same field. Hopefully a new build that fixes ... should fix this issue. support Support Thank you for making a build that contains the fix available ... all indexes) should fix the corrupted indexes. Also, can we assume that all version prior to 2.6.4_02

ObjectDB 2.1 has been released and it includes important additions and fixes : Added Online Backup ... ( 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

/ticket/1823) You had attempted to fix it in build 2.6.6_08. I reported today on investigations by version ... object" when using a TableGenerator. That problem was demonstrated by the provided test case, fixed ... Dr Darren Kelly The bug was found and fixed in build 2.6.9_01. It can affect any application

fixes this issue. support Support Build 2.5.5_01 fixes this issue but it has a new bug. When I ... .5_01. mosi0815 Ralph Moser The new error is not related to the Enhancer fix , but to another fix

workaround or could this be fixed ? Is the last (problematic) query invalid from your point of view? Thanks ... this fix /workaround in the test scenario, still trying to establish it in the "real" project. There I ... the queried root entity). I will post a thread there to see if someone can fix it. For so long I

Your report shows two different issues. Please try build 2.5.5_04 that includes an attempt to fix them. support Support Thanks for the fix . It helped for the above mistakes, but next one raised 200MB ... the HashMap. Can this be fixed too?  jakab Gergely Jakab This map issue

.) java -Xmx100G -Djava.io.tmpdir=$tmpdir -cp objectdb.jar com.objectdb.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

. Please try version 2.0.5 that fixes the problem. support Support Thank you for your reactivity.   ... and that don't fix the issue. I try it with the test application and my full application. In both case the bug is still there.   Do you check if the new version fixes the problem on the test

=. Build 2.4.7_17 fixes this behavior. support Support Thanks for the quick fix . This new version 2.4.7_17 fixes this issue. pezifromvienna Peter Sauer

after fixing the relationship on the Document side to:     @OneToMany(mappedBy="document ... of the collection fixed the issue! thank you very much for your great help. farid oudjanef Farid Oudjane ... that should fix it. support Support I will try that. Thanks Farid oudjanef Farid Oudjane

- the information should be used to fix the application. To fix broken references (i.e. to replace broken ... . This cannot replace fixing the application but it is an easy way to repair a specific database. support

fixed an issue with queries ( issue #2858 ) but had a known query performance regression. It was fixed ... that has not been fixed . Changes in versions 2.8.9_03 - 2.8.9_06 are not expected to affect queries. An attempt

cache is fixed and not released by ObjectDB. You can try reducing its size.  Are you sure ... faults and fix them, but the soft references to entity objects behaviour seems normal.   ... that may be created.  I also understand that those PAGs are fixed and ObjectDB will not free them.  I

to fix the DB file, the Doctor deleted all listed instances of TC. Could u please help me clarify ... _05 it might be the critical schema bug ( issue #2621 ) that was fixed in version 2.8.4. Please try ... did not help. We tried to open a DB with already corrupted data (by the schema change, without fixing

Support build 2.7.1_08 does not fix the problem. sjzlondon Steve Zara You are right, sorry. It fixed a simplified test case but not your exact test case. Build 2.7.1_09 should fix your test case as

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

) relationships ( issue #769 ). Improved performance of database file extending. Fixed a bug in ignoring global cascade persist in an ORM file. Fixed a NullPointerException during query execution ( issue #978 ). Fixed a class loading issue during automatic class scanning. Fixed a Doctor deadlock . Fixed

property method names . Fixed a bug in retrieving pure time values (java.sql.Time). Fixed a bug in MEMBER OF queries on embedded objects. Fixed a bug in querying indexed nested embedded objects. Fixed a bug in querying enhanced embeddable classes. Fixed server crash on exceeding maximum number

that might fix it (see #2)? support Support I tried version 2.2.6_01 and it did NOT fix ... addition, please notice that this attempt to fix the problem was done without the ability to reproduce ... Support Yes, after complete library reassignment and rebuild 2.2.6_01 did fix it. Sorry, i did

to the Server and Explorer About dialog boxes. Fixed an UPDATE/DELETE query bug in client-server mode. Fixed an ArrayIndexOutOfBoundsException in retrieval of large objects. Fixed Explorer display of user defined serializable objects. Fixed a bug in using NOT NULL in criteria queries . Fixed a bug

FETCH to act as LEFT JOIN in path expressions. Updated the PDF manual. Fixed a possible deadlock on Schema Update during Multithreading activity ( issue #1139 ). Fixed a bug in loading mapped (inverse) to-many relationship into an array field ([]) ( issue #1131 ). Fixed a bug in loading mapped (inverse

Improved performance of collection and map size evaluation in queries. Fixed a critical bug in page caching (issues #610 , #621 , #625 ). Fixed a bug in optimization of non ASCII string indexes. Fixed the new query HOUR function to return hours as 0 to 23 (using 24-hour clock). Fixed a regression

Added support for JTA and Java EE Containers ( issue #8 ). Fixed a bug in indexing entity objects. Fixed a bug in fixing broken references in ObjectDB Doctor. Fixed a bug in modifying enhanced detached embedded objects. Fixed a spring transformer (LoadTimeWeaver) problem. Fixed a class

to memory leak ( issue #453 ). Completed missing documentation (e.g. UPDATE & DELETE queries). Fixed memory leak issues. Fixed server hang and deadlock issues. Fixed several NullPointerException bugs. Fixed the "Failed to generate dynamic type" exception. Fixed a bug in query plans that use

. Improved field type error and internal error messages. Improved the Doctor output. Fixed a bug in using inner classes for query results. Fixed an error due to to an unused type referencing a deleted type. Fixed a primary key query issue. Fixed a bug in comparing embedded objects in queries ( issue

Fixed a bug in "p.id IN :ids" queries. Fixed a bug in handling NOT =  queries ( issue #536 ). Fixed ClassCastException and NullPointerException in using a composite index in queries ( issue #531 ). Fixed Explorer bugs: editing embedded objects and using connection urls. Fixed

Added support for integration with WebSphere / Liberty application server. Fixed deletin g large transaction temporary files (in the experimental large transactions feature ). Fixed empty log directory creation when logging is disabled. Fixed a bug in using nested embedded objects. Fixed a query

Fixed a critical bug in extensive removal operations of large objects. Improved the performance of navigation through an inverse (mapped by) field if the owner field is indexed. Fixed a LEFT OUTER JOIN bug . Fixed a bug in parsing queries with parenthesis followed by NOT . Fixed a bug in running

and provide a fix . support Support The reason for not using the composite index was found and can be fixed .  As there are too many possible combinations for covering the filter: "a.type = 0 ... combinations to 10000 solves this issue so a quick fix is possible for this specific issue

of pessimistic locks on client-server connection failure. Fixed an OptimisticLockException bug on commit after flushing a removed modified entity object. Fixed a  NullPointerExeption on new index building . Fixed a NullPointerExeption on flush ( issue #1840 ). Fixed a bug in using temporary files in

Fixed Java Agent / Java EE / Spring enhancement bug. Fixed a bug in merging detached entity objects. Fixed unexpected  NullPointerException in client server mode. Fixed an exception in AVG query on non numeric values ( issue #107 ). Fixed a bug in handling JOIN queries with primary key fields.

ObjectDB 2.3.x to 2.5.2. Corruption of the database that cannot be fixed by the Doctor (due to the  ... .3.x would be a problem because development work I did this year relies on fixes and enhancements ... in the log after that restart, so hopefully the Doctor fixed these index issues. In that case

Fixed an issue with viewing class Ids in the Explorer (see issue #2677 ). Fixed a regression bug (in version 2.8.5) in using AS in JOIN ( issue #2666 ). Fixed a connection pool issue related to memory release ( issue #2663 ). Fixed an Enhancer issue in supporting Java 9 modules and packages

) and either start with a clean database or fix this database by running the Doctor in repair mode (and then verify the fix by using the Doctor in diagnosis mode). Check if your application can bring ... Following your report I could reproduce the exception, I found the bug and fixed the problem. Version 2

the problems with these 2 Person instances without throwing an exception, but fixing these instances ... . support Support Build 2.4.0_02 fixes the Doctor as explained above. support Support I tried the new ... :22) [ObjectDB 2.4.0_02] null lorenz2304 Benjamin Lorenz You are right. The previous fix handled

require changing our large existing JDO 1.2 codebase. spiffy Jonathan Harley Build 2.4.7_04 fixes ... classes, should they use the package name? Maybe also the class name? This could be easily fixed if this is how it works in other JDO implementations. support Support Confirmed that 2.4.7_04 fixes

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 in using persistent properties with incomplete enhancement.

? Could you please provide the parameter values for getting the first exception? support Support I could fix ... parameters for testing the first query and if the problem is solved a new build with the fix ... Ralph Moser Please try build 2.3.1_04 that should fix these exceptions. For the following query

other recent builds, but to issue #1818 , that was already fixed . It is unclear why the previous fix is not ... correct. Thank you for the fix . btc_es BTC EmbeddedSystems

. Is it possible that your application has a similar condition? Build 2.6.1_01 should fix this exception ... should fix this issue. If the exceptions in your application are due to modifying a persistent collection ... ; support Support Thank You. 2.6.1_02 fix our problem. Now come no more errors. btc_es BTC EmbeddedSystems

continue that discussion on that thread. felixobjectdb Richard Szurgot Yes, this should be fixed in one of the next builds. support Support Any idea when this will be fixed ? bensteele Ben Steele No immediate fix is currently planned. The workaround is to make sure that every new (or modified) type

;      int x;     } } Build 2.6.0_04 includes a fix of this issue ... is still not fixed . wua Andreas Wurm You are right, sorry. Somehow the fix has not been integrated

automatic schema evolution of enum fields. Fixed A NullPointException when using EntityManagerFactory with different class loaders. Fixed a missing call to @PostUpdate when object change is detached by  JDOHelper.makeDirty . Fixed opening context menu in the Explorer.

. This requires fixing the application (making sure that references to deleted objects are removed ... , it wouldn't be easy to find and fix it. If you can share your test so we will be able ... , we may be able to understand and fix the issue. support Support Hello, we have another fresh