Internal Website Search
51-60 of 200 resultsRefreshSignificant I/O costs during batch update or insert data. Our application has some complex entities. We do batch update(merge detached entity) every 2 minutes. We find the period significant IO costs these days, and disappeared when turn off the batch updating. 1.ObjectDB is in embedded mode. 2.ObjectDB version is 2.3 | |
Auto Date for Creation and Update Hi, is there a way with objectdb to use annotations so that - automatically - the creation Date gets updated once only and the change Date on each change ... > tlehmann Thomas Lehmann You may be able to update these time | |
Intermittent Exception "Attempt to update types in read only mode" Attempt to update types in read only mode (error 614) at com.objectdb.jpa.EMF ... : Attempt to update types in read only mode at com.objectdb.o.MSG.d(MSG.java:61 | |
Multiple Collection Fields not update correctly works. But when updating(merging existing record) somehow the rotation overrides the position | |
Getting Unexpected internal exception when updating entity in MEM db.radius.cc.server.db.RtDB.Update(RtDB.java:101) ... 10 more Caused by: java.lang | |
Update Entity references if we change the type of an entity will be marked as dirty and changes will be committed. So after the database update your application | |
Schema Update: class hierarchy change> support Support Thanks for the Update. Now it works. How can data be saved | |
schema update procedure Is there a specific procedure that we should follow when making schema updates? I have often found that it takes several restarts of the the server to complete the change. The issue is that there may be changes in many places. Each change appears to be applied as the class | |
JPQL Update & Delete (JPA 1.0) JPQL (Java Persistence Query Language) supports updating and deleting database objects by queries. Currently ObjectDB supports only JPQL SELECT (retrieval) queries.Delete ... one of the next builds. support Support Implementation of both DELETE and UPDATE | |
Indexes broken after schema update, whether or not the entity was updated, etc.). support Support I'll dig |