ObjectDB ObjectDB

Internal Website Search

131-140 of 200 resultsRefresh

em.flush(); em.clear(); loosing data and not persisting managed objects

that I'm using in these entity has multiple fields that are related but takes too long to access ... with String Primary Keys, I'm going to try the other multi ID method of @IdClass and multiple @Id

Inserted entities with strings as keys and indices needs more and more ram memory in comparing to primitive integers as keys and indices

@GeneratedValue primary keys are sequential. So when you persist multiple new objects their primary keys ... primary keys are sequential. So when you persist multiple new objects their primary keys are sequential

On ensuring ID available after persist

allocation to commit or flush - multiple IDs for multiple objects can be allocated together in

Searching lists within objects

: Avoid multiple Attribute instances with identical type / value by defining a composite unique ... such comparison, so it might be still more efficient to use multiple JOINs in this case. support Support Okay

How to open a running db in ObjectDB Explorer?

multiple processes (embedded mode supports concurrently only within a JVM, i.e. multithreading, but not ... embedded mode, client server mode supports accessing a database concurrently from multiple processes

ArrayIndexOutOfBoundsException at com.objectdb.o.ALS.c(ALS.java:89)

it is more efficient to create a single EntityManagerFactory with multiple EntityManager instances. It is uncommon to create multiple EntityManagerFactory instances as demonstrated by your code. support Support

Query in JPA2 with LEFT JOIN on INNER JOIN

left join action_profile ap9 on ap9.id_action=a.id and ap9.id_profile=9; How to specify multiple conditions on left join ? faber Faber You cannot specify multiple conditions on left join in JPQL

Performance tuning, best practices

user with that specific operation? ObjectDB can use multiple cores to serve concurrent requests from different users, and also tries to use multiple cores for a single request, but the later

objectdb.home for client/server

where our object db home is located at as we might have multiple server instances running on multiple

Internal error

of one PersistenceManager by multiple threads and / or other PersistenceManager instances. You wrote: > Both threads ... cause of this exception is sharing entity objects of one PersistenceManager by multiple threads and / or

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support