ObjectDB Database Search

are not completely clear . Please follow the posting instructions and provide a minimal runnable test

is clear . This solution could work with multiple applications only if all the applications always select

completely clear . A blocked thread is not necessarily a problem. There is an essential synchronized

such a large object results in an exception as the one you got, with no clear error message

I've had a quick read through the features/FAQ and haven't been able to find a clear answer. I'm looking at replacing a setup of H2 where I have 40GB in-memory backed by 800GB on-disk, the 40GB in memory represents the first 40GB of the 800GB on-disk for super-fast recent entry searching

(as it will be clear that location is embedded and not a separate entity when looking

% of the occasions in which this exception is thrown, and in these cases the exception is clear

;    em. clear ();         TypedQuery q = em

the configuration , so strong references will be used automatically until the persistence context is cleared

to overcome the problem by using flush(), clear () and refresh()  hgzwicker Hans-Georg Zwicker Good

, clearing list fields and keeping orphan objects is the database (if understood correctly) is possible

a different order, so that can cause a deadlock. Now that the issue is clear we hope to be able

Hello, As stated above, I would like to know if it is possible to commit only specific elements, or at least update a single table, disregarding the other entities loaded in the persistency context? I have a complex hierarchy of intertwined objects. Currently I am clearing my persistency context

clear to me which one is used). 2) Docker containers are assigned MAC addresses as explained

, and clearing the EntityManager at transaction end. support Support Hi Great support .. thanks for the timely

are fast and object reusing doesn't usually improve performance. If you can show clear benefits in

since it is a different topic than the original post. support Support So to be clear ... columns are created

; originalOrganisation.getElectronicAddresses(). clear ();          

for each, and possibly also  clear  after commit ) Using classes that are not enhanced. In

this specific case is in the query or in ObjectDB. It is clear , however, that $3 should be replaced

Hans-Georg Zwicker From your description it is quite clear that the exception is related to opening