ObjectDB Database Search

multiple threads. So yeah, without some intense analysis (we're talking hundreds of fields with many layers

, especially around 20 TB and above , it is strongly recommended to partition data across multiple databases

) and it is done repeatedly in multiple starts of database without any indexing change. We would need

of one writer and multiple readers provides better performance because the coordination between the servers

are always slower because multiple entities are involved. You can improve the performance of queries by using

I'am new to study JDO. Can and How I use JDO an distributed transaction?( multiple database)。 Is ObjectDB also provided JCA util just like DataNucleus? Reference：     Spring Framework Reference Documentation       JCA, JTA, and JDO Transactions - Using

same machine.   This is happening if multiple thread(20-50) accessing db parallelly for 30-40 min

by ObjectDB, as the supported replication is based on one master and multiple slaves

creates multiple PersistenceManagerFactory instances and some of them are not closed. support Support

We've got this exception, when running DB Doctor in parallel on multiple DB files. com.objectdb.o.UserException: Attempt to open a non existing file './tmp.E3Mwf13d7o/objectdb_7666012114926572695/DoctorSection_0.fls' at com.objectdb.o.MSG.a(MSG.java:64) at com.objectdb.o.LFL.x(LFL.java:809) at com

must be composed from the parent Id and the child subkey. And I have multiple child subtypes in which child

that, because we are using multiple separate ObjectDB Servers. Any server is responsible for managing few DB files

We encountered an issue that caused an outage last Friday on multiple ObjectDb server instances. The problem occurred while trying to close the EMF to three separate ODB databases, residing on different ObjectDb Servers,  the exceptions were thrown on two of our servers (TransactionServers

class loader or multiple class loaders? Please verify that you close every EntityManager

one EntityManagerFactory instance, use it for creating multiple EntityManager instances, and remember to close each

Added support for a JPQL update query with multiple variables (issues #2369, #3009)

I am encountering problems (complexities) with EntityManager registration of entities across multiple modules in a multi-module Maven project. I have a  entities under many different paths in many different modules, and frequently evolving/changing. JPA2 persistence.xml does not

different parts of their projects in several enhancement runs). If multiple enhancement runs are allowed