Fast Object Database for Java - with JPA/JDO support

Internal Website Search

101-110 of 200 resultsRefresh

Removing of an entity removes also another entity type

. All ResolverMapping entities are removed by a query (DELETE FROM ...), afterwards ResolverMapping entities ... . If the ToleranceDefinition entity is removed from database by a query (DELETE FROM ...) then it performs. The data ... .1_03. btc_es BTC EmbeddedSystems OK. Thanks for the update. Please note that mixing direct DELETE

Method Invocation On All Entities

Deleting or changing a field of all the entities of some type is fairly easy, using the DELETE ... should do some operations before it gets deleted, and at some point we want to delete all those entities. It could be usefull if we could invoke some "doBeforeDie" method before the deletion. One way to achive

Date field Index is corrupted due to time change

Hi, can you shed some light on why we cannot delete data from the attached DB file. A delete ... , so the error message that you got on an attempt to delete objects could happen with other operations as ... in 2.6.4_12 (and of course 2.6.5). The delete query we run is: DELETE FROM RecordingMetaData

Performance and memory usage of queries

requires so much memory. In the implementation of our UnitTests we have used "DELETE FROM Object" to delete ... .setFlushMode(FlushModeType.AUTO);   em.getTransaction().begin();   Query q = em.createQuery("DELETE FROM ... mentioning my similar experience. I remember I had an issue several times with deleting many object

Removed entities can be found by query in the same transaction

__odbtracker/m (type STA, value=Persistent-Deleted-Flushed) which shows that the entity is deleted ... what is the problem? best regards BTC btc_es BTC EmbeddedSystems If an entity was deleted from ... at least two different snapshots of objects - one with the deleted object and the other without the deleted object

Server closes if large query runs out of memory

during JDO deletion query, and the temp threshold was set and was low (64mb). There is an easy work-around, which is to divide up the deletion into smaller number of objects. I understand that JPA bulk delete doesn't involve any object retrieval, whereas perhaps JDO deletion does. Would using JPA for large


Method javax.jdo.spi.PersistenceCapable boolean jdoIsDirty() Tests whether this object is dirty. Instances that have been modified, deleted, or newly made persistent in the current transaction return true. Transient instances return false. Returns: true if this instance has been modified in


Method javax.jdo.spi.StateManager boolean isDirty( PersistenceCapable pc ) Tests whether this object is dirty. Instances that have been modified, deleted, or newly made persistent in the current transaction return true. Transient nontransactional instances return false. Parameters: pc - the calling


Method javax.persistence.EntityManager Query createNativeQuery( String sqlString ) Create an instance of Query for executing a native SQL statement, e.g., for update or delete. Parameters: sqlString - a native SQL query string Returns: the new query instance Since: JPA 1.0


javax.jdo.annotations Enum ForeignKeyAction java.lang.Object java.lang.Enum javax.jdo.annotations.ForeignKeyAction Implemented Interfaces: Serializable, Comparable Enumeration of the foreign-key delete/update action values

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