ObjectDB ObjectDB

Internal Website Search

181-190 of 200 resultsRefresh

InternalException when reading a HashMap

helped unfortunatelly. What helped was deleting the entity completely in explorer including all it's instances (deleting only instances did not helped) But that way we found, that another entities

OutofMemory error with Object DB 2.0

" password="admin"> <dir path="/" permissions="access,modify,create,delete" /> </user> <user ... ,delete"> <quota directories="5" files="20" disk-space="5mb" /> </dir> </user> <user

Is it ok to put list or map of embeddable objects in entity ?

>()) on an entity that had some Class_B instances in bList? Will they be deleted correctly from database ... previous content is automatically deleted. To see serialzable objects in the Explorer try to add

com.objectdb.o.UserException: Ambiguous entity name

remove this embeddable class without deleting my database or deleting the entity it was related

unable to connect to remote server using VPN

,create,delete" /> </user> <user username="$default" password="$$$###" ip=""> <dir path="/$user/" permissions="access,modify,create,delete"> <quota directories="5" files="20

Database Inconsistency or corruption

) It seems that all Attributes of the updated ObjectValue are just deleted from the database. If I had detailled traces of the EntityManager or of ObjectDB, I could identified when the delete operation is executed

One transaction or two?

If I have a large number of objects to delete and then add to a PersistenceManager is it more efficient to do everything in one transaction or two? Currently my code looks like ... ().rollback(); } if(!pm.isClosed()) { pm.close(); } } Should I separate the deletes

NullPointer when accessing entity field

way: for single read/write/update/delete: - we create new EntityManager, do the operation in ... ,delete from ThreadLocal and close EM So I think there is now concurrent access on one EntityManager. In

Unexpected Exception (Error 990) with ArrayIndexOutOfBoundsException

Query queryDelete = em .createQuery("DELETE FROM EventLogPersistEntry p WHERE p.id ... to the ObjectDb. I did not delete the Database file during these changes. The system where that error occured

again merger missing logs + objectdb exception

on both sides (for performance reasons) - some of these references are broken when we delete objects ... of maintaining these specific references on deleting are very high. is there a problem to have this kind

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