ObjectDB Database Search

,   just tried the fixed version. Two notes: 1. For a composite key an instance of the target ... ); // false tsichevski Vladimir Tsichevski Point 2 is indeed a bug. Build 2.4.7_09 fixes ... you for fixing previous problems. Here is a new one. Using the same class structure as in my previous posts

Because of this lock all DB operations were only waiting and we could fix it only via restart of whole application ... them. When a circular lock is found, we should be able to fix the deadlock. If you can verify

an issue (a bug report in the Issue Tracking system)? CBE CBE Build 2.6.8_07 should fix this issue. Thank you for the report. support Support Confirmed.  The fix works for me.  Thanks! CBE CBE

java I assume that if I'll back up the .odb file, delete it and then restore it will fix the issue ... . It looks like the problem is fixed when I close the entityManagerFactory manually (using a dedicated

to run your test. support Support Build 2.2.9_05 includes an attempt to fix the NullPointerException . The fix is based on the stack trace rather than on the test case since running the test project

a persistence.xml file for objectDB fixes the problem. In my case the fix was simple, for all other JPA impl

to the plugin runtime classpath. Fixing   "SELECT p FROM Point p" to  "SELECT p FROM Pilot p ... . It seems that the test works now: support Support Hi Yes it works now thank you. I fixed that obvious bug

_17 should fix this deadlock. support Support could we have some more details as to what has changed ... that was added in build 2.4.4_10 to fix another problem caused the deadlock. All builds pass the same

[Tools Options] dialog box when no database is open. A fix will be available soon in ... build 2.4.0_01 that should fix both issues. support Support thank you for the post, I hava

, because we use inheritance a lot. Is it possible that you can provide a fix ?. We think it must be possible ... if a referenced entity have a reference to another entity) We need a fix that fulfills

of a super class is used by the query program. Version 2.2.9 fixes this bug. Thank you for this report ... an improved fix . support Support Looks like this version works. Thanks, Eitan eitane Eitan Eibschutz

) " fixes " this problem. Only id from both entities cause this exception. Can I somehow check the type ... 2.2.8_01. support Support New version works fine. Thanks for a fix . lwalkowski Lukasz Walkowski

are removed from the cache and then retrieved again, fixing the broken relationship). When using a short ... only the owner side can cause this strange behavior. Notice that this can be fixed by forcing retrieval

build 09 that should fix this issue. In addition, you might want to enhance your entity classes ... , thank you for the report. Please check the new build that should fix it. support Support

the browser at http://localhost:8080/Guestbook and observe (and please fix !) the 404 error!   Thanks ... at all from from eclipse with tomcat6 because I just get 404 errors. I'm hopeful that once we fix

; pedwards Paul Edwards Appears this has been fixed in 2.2.8_06, I was only using 2.2.8_02 pedwards Paul Edwards OK. Maybe it is related to some of the bugs that were fixed in the last builds. support Support

by ObjectDB for inverse (mapped by) collections. Please try build 2.2.6_04 that should fix ... should update both sides anyway). support Support In build 2.2.6_05 is it fixed , thank you. Michael anaq x

the image correctly but it was set as private due to permission issues. This was fixed now ... is simply skipped in some cases due to a race condition you will have to check on your side how to fix it (e

The last builds include fixes for some fetch issues so it is possible that ObjectDB behaves differently ... source code instead of as an attachment is preferred). Please try build 2.3.5_05 that should fix this issue. support Support

2.4.3_01 (as a result of fixing another problem ). Please try build 2.4.3_04 that should fix the new problem. support Support

, run the ObjectDB Doctor (in fix mode) to build the index (otherwise the index will not be used). By ... ;This does mean that we need to get things like this indexing bug sorted out soon.  If we can fix

). This could be the result fixes in build 2.3.5_* and 2.3.6_*. Is this issue new? Does it happen ... , and this can be fixed by setting the configuration. The following configuration elements are particularly relevant

something that may cause this issue, and build 2.6.2_05 should fix it. If you get these errors again with build 2.6 ... with the previous fix .   Stacktrace 1: pos = 4107765760 length = 2048 Failed to read from file '/path_to_db

The criteria query AND/OR fix in 2.2.8_04 caused this new problem. Please try build 2.2.8_05 that should fix it. support Support    This release carries out the grouping and likes correctly.   Thanks!   Willks William

externally on Tomcat. Please try ObjectDB 2.0.3 build 02 that might fix this issue ... That fixed it!  Thank you so much. gorilla77 Ji Kim Good. Thank you for this report. support Support

relating to objectdb from the supplementary plugin to the main plugin plus a few fixes allowed

that was just released (2.2.0_03) fixes the main problems and seems to work well with JBoss AS 6.0

You have to fix the connection url. See: https://www.objectdb.com/java/jpa/persistence/overview

. They are replaced with null values when the database is fixed using the Doctor. In this specific

!?? How could that have happened and what are we supposed to do now to fix this as when quering those entities

;directory). Add to the persistence.xml file a request to load the ObjectDB module. Build 2.4.3 fixes

the database file - it may be possible to fix it manually. support Support

;query.getSingleResult(); or the new build (2.2.7_07) that should fix it. Thank you for this report

though) -Objectdb v2.4.0_03 -db was converted from 1.04 then fixed by the Doctor with no errors. -I

). Supporting such structures will require some fix in ObjectDB, but since it is not allowed by JPA

;Hopefully it will be fixed soon. Thank you for this report. support Support

. Fixed a bug in reflection mode in detecting changes after flush ( issue #1602 ). Fixed a NullPointerException is merging objects of new types . Fixed a bug in managing inverse (mapped by) collections and maps in reflection mode.

- this is the preferred solution (assuming this is indeed the problem). support Support Build 2.3.6_14 fixes ... after retrieving the BeitragVertragArt class, changing some fields and writing it back? The fix in _14 fixes the Explorer only, right? quasado Alexander Adam If you have a problem in retrieval

A possible deadlock was detected when new types are registered during multithreading activity against ObjectDB. Until this issue is fixed , the recommended workaround is to complete registration ... (); The last command will work when ObjectDB can find managed classes automatically . support Support Version 2.5.1 should fix this issue. support Support

.RandomAccessFile. (Unknown Source) at com.objectdb.o.LFL.D(LFL.java:855) ... 37 more Please provide a fix ... Support Thank you very much for the fast fix . We had directly used the new version. btc_es BTC EmbeddedSystems

another attempt to fix the issue (the chance that this is what will solve the issue is not high ... . Build 2.9.0_02 fixed the original issue by adding a synchronized block, which apparently

on accessing an inverse collection in an entity that has been garbage collected. Build 2.3.2_01 fixes ... Francis Thank you for the test case. Build 2.2.3_05 should fix the problem. support Support

that should fix this bug. support Support Thanks. That fixed the bug. doppelrittberger Markus Ritter

_04 should fix this problem. support Support Thanks - that fixed the test but unfortunately I

you for your report. Build 2.2.5_09 should fix this NullPointerException . support Support Thank you for a quick turnaround. I can confirm it fixed using Build 2.2.5_10 longpat Brian O'Hare

Added support of embedded path expressions to  mappedBy  fields ( issue #2917 ) Fixed the SectionClassifier retrieval bug ( issue #2912 ). Fixed log file location for some server log messages ( issue #2914 ).

. Please try build 2.3.5_04 that should fix this new issue. support Support

Confirming, fixed in 2.6.5 release! Bug may be closed. Harman Alexander Golyshkin

Added empty implementation of new JPA 2.1 methods. Implemented new JPA 2.1 EntityManagerFactory methods:  createEntityManager , unwrap . Improved retrieving persistent string fields by using "".intern() for empty strings. Fixed a bug in queries on composed embedded primary key ( issue #1301 ).

is fixed ). There is a chance that a synchronized block that was added recently may solve the problem