ObjectDB ObjectDB

Internal Website Search

21-30 of 200 resultsRefresh
88

UPDATE query to set a new field after schema change

) property to false for all existing entities in the DB. I tried to execute an update statement with the Explorer tool. The statement ends and tells me that 1000 entities have been updated. I then save ... UPDATE queries can only update existing fields, and old objects that do not have the fields are not
88

Updating existing persistence entries

: Attempt to reuse an existing primary key value which makes sense to me but I'm missing a em.update() method. I found examples for updating objects in the knowledge base, but they make use of a pe ... the new manual that also includes instructions on how to update and object using JPA. support
86

Unexpected behaviour upon update. Bug?

public class Update implements Serializable { @Id int i; int v; public ... (); em.getTransaction().begin(); Update simple = new Update(); simple.i = 0 ... Update s" , Update.class)             .getResultList().listIterator
86

Bulk Delete and Update - best practice?

. The attachment also contains an update test which has similar memory problems. I'm running both tests with the default objectdb.conf. In general is an UPDATE/DELETE statement the most efficient way to update/remove a large number of objects? I've had success with the "drop" keyword in
86

Not able to update records

Hi, I am tring to update the simple object by using Update query by i am getting following exception [ObjectDB 2.4.4_15] javax.persistence.TransactionRequiredException Attempt to run update query ... sqlQuery = new StringBuffer("UPDATE UserCredential p "); sqlQuery.append(" SET sessionID
85

How to disable Transparent Update.

How to disable Transparent Update. I have done 2 task in a single transaction. 1. Find a entity by a em.find(Class<t> cls,Object o) and change some fields.(not updating) 2. Persist a new entity. But i found the in 1st case the changed value was updated. I have attached the sample program
85

OutOfMemoryError on search after update on DB created with DB Doctor

about 540 thousand records. At this stage there is no problem when searching and updating. 3. We run ... . Try a searching and all appears to be fine. 6. Do an update, any update to any record and all appears to be fine. 7. Do a search after the update, any search and CPU use shoots up to > 100% use
17

UPDATE query cannot set a new field after schema change

) property to false for all existing entities in the DB. I tried to execute an update statement with the Explorer tool. The statement ends and tells me that 1000 entities have been updated. I then save ... UPDATE queries can only update existing fields, and old objects that do not have the fields are not
17

Update query null error

it still does not work, using (directly in explorer) Update Action a Set a.transferred = 0 ... Update Action Set transferred = 0 here objectsInCharge.nodePath like "/(PR)W4455NS01 ... %" Update Action a Set a.transferred = 0 where a.objectsInCharge.nodePath like "/(CR)70005
17

Database Management Settings

" synchronized="false" />   <index-update enabled="true" priority="40" /> <query-cache results ... , to avoid thread competition that leads to poor performance. The <index-update> element   <index-update enabled="true" priority="40" /> The <index-update> element specifies how newly defined indexes

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