ObjectDB Database Search

deleted the tmp file of another application. I hope this description is sufficient. EKK EKK Emmanuel Keskes ObjectDB deletes its temporary files in 2 ways: Every process deletes its own temporary files that become unreachable (tracked by using weak references). When a process starts it tries to delete

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

Hi, can you shed some light on why we cannot delete data from the attached DB file. A delete ... on an attempt to delete objects could happen with other operations as well. The common reason for database ... ; The delete query we run is: DELETE FROM RecordingMetaData The exception is the same: [ObjectDB 2.6.5

occurred 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

Hello All, I am getting the constraint violation exception whil deleting the entries I ... need to delete   records in both tables (TransportationEvent and Conclusion) here i am trying to delete conclusion table records like bellow: removeConclusions(conclusion.getId()); public void

to Parent, so that when the parent is deleted all children are removed as well. Unfortunately, in ... the following case not all children are deleted : ... Parent parent = new Parent(); parentRepository ... is persisted parentRepository. delete (parent); // Here trying to delete the parent

; common.model.UserSession$_ delete _closure1     mr.model.MRAuction$_ delete _closure2     mr.model.MRAuction$_ delete _closure3     mr.model.MRAuction$_ delete _closure4     mr.model.MRAuction$_ delete _closure5     mr.model.MRAuction

. They were present before and also saved in the DB, but are deleted for some time now. When I open the DB ...  ? jakab Gergely Jakab You can delete old classes using the Explorer of version 2.8.3_05 (right click - Delete , or from the Edit menu). Please check if this solves the issue. support Support I

that there are no already deleted objects in the graph to delete but it still didn't work. As you can see my testcase does ... because, in the same transaction, I gather an Extent, delete an object, then try to gather the same ... that was deleted . The fix was to do a PersistenceManager.flush() before trying to gather the Extent

. - If it's an update to an existing track, delete the entire previous entry and then add in the new ... more embedded objects whenever possible. Delaying the delete operations to time with less or no activity (and if you can use one transaction for deletion of many updates it can also improve performance

erase the DB and start all over. But that's a problem. I have discovered it when I had to delete and set the new database in production. It just didn't want to respect the restrictions. I had to delete ... . Otherwise I can't do it. What is it to be done? zmirc Mircea Chirac will not delete classes

to null except the primary key. The same behavior is when we  delete with a query use entityManager ... ;explicitly, in addition to deleting it. However, if the set is defined as mapped by , it will be updated automatically after committing the delete operation and then reloading of the object that contains

;     private boolean deleted ;     private Date modificationTS ... ------------------- [1] Page #19753 entry 0 has unexpected field count (7 instead of 5) 0. oid = '567651' 1. deleted ... #33279 entry 1 has unexpected field count (7 instead of 5) 0. oid = '559770' 1. deleted = false 2

.AbstractCallSite.callGetProperty(AbstractCallSite.java:296) at app.database.ObjectDbDatabase. delete _all_entities(ObjectDbDatabase.groovy:69) at app.framework.Database$ delete _all_entities$0 ... (AbstractCallSite.java:296) at app.database.ObjectDbDatabase. delete _all_entities(ObjectDbDatabase.groovy:69) at app

JPA Method in jakarta.persistence.criteria.CriteriaDelete CriteriaDelete where (   Predicate... restrictions ) Modify the DELETE query to restrict the target of the deletion according ... removed. Parameters: restrictions - zero or more restriction predicates Return: the modified delete query Since: JPA 2.1

JPA Method in jakarta.persistence.criteria.CriteriaDelete CriteriaDelete where (    Expression  restriction ) Modify the DELETE query to restrict the target of the deletion according ... . Parameters: restriction - a simple or compound boolean expression Return: the modified delete query Since: JPA 2.1

 deleteQuery ) Create an instance of Query for executing a criteria delete query. Parameters: deleteQuery - a criteria delete query object Return: the new query instance Throws: IllegalArgumentException - if the delete query is found to be invalid Since: JPA 2.1

[ ( {, } ... ) ] [ ON UPDATE ] [ ON DELETE ] When the ConstraintMode value is CONSTRAINT ... and delete actions it determines most appropriate for the join column(s) to which the foreign key ... . If the foreignKeyDefinition element is not specified, the provider will generate a constraint whose update and delete

 deleteQuery ) Create an instance of Query for executing a criteria delete query. Parameters: deleteQuery - a criteria delete query object Return: the new query instance Throws: IllegalArgumentException - if the delete query is found to be invalid Since: JPA 2.1

JPA Method in jakarta.persistence.criteria.CriteriaDelete Root from (    EntityType  entity ) Create and add a query root corresponding to the entity that is the target of the DELETE . A CriteriaDelete object has a single root, the entity that is being deleted . Parameters: entity

JPA Method in jakarta.persistence.criteria.CriteriaDelete Root from (   Class  entityClass ) Create and add a query root corresponding to the entity that is the target of the DELETE . A CriteriaDelete object has a single root, the entity that is being deleted . Parameters: entityClass

(Non-repeatable read): Transaction T1 reads a row. Another transaction T2 then modifies or deletes ... . Another transaction T2 then modifies or deletes that row, before T1 has committed or rolled back. A lock

.deleteInOpenTransaction(ObjectCacheDB.java:361) at com.ysoft.cache.objectdb.ObjectCacheDB. delete (ObjectCacheDB.java:356) at com.ysoft.cache.objectdb.ObjectCacheDB. delete (ObjectCacheDB.java:347) at eu.ysoft.safeq.ors.CacheDBWrapper. delete (CacheDBWrapper.java:73) at ysoft.sqcore.job.CacheJobManager

JPA Method in jakarta.persistence.Query int executeUpdate () Execute an update or delete statement. Return: the number of entities updated or deleted Throws: IllegalStateException - if called for a Jakarta Persistence query language SELECT statement or for a criteria query

a CriteriaDelete query object to perform a bulk delete operation. Parameters: targetEntity - target type for delete operation Return: the query object Since: JPA 2.1 CriteriaUpdate

JPA Method in jakarta.persistence.criteria.CriteriaBuilder CriteriaDelete createCriteriaDelete (   Class  targetEntity ) Create a CriteriaDelete query object to perform a bulk delete operation. Parameters: targetEntity - target type for delete operation Return: the query object Since: JPA 2.1

JPA Method in jakarta.persistence.EntityManager Query createNativeQuery (   String sqlString ) Create an instance of Query for executing a native SQL statement, e.g., for update or delete . If the query is not an update or delete query, query execution will result in each row

Throws: IllegalStateException - if called for a Jakarta Persistence query language UPDATE or DELETE

Persistence query language UPDATE or DELETE statement QueryTimeoutException - if the query execution

DELETE statement QueryTimeoutException - if the query execution exceeds the query timeout value set

for a Jakarta Persistence query language UPDATE or DELETE statement QueryTimeoutException - if the query

Persistence query language UPDATE or DELETE statement QueryTimeoutException - if the query execution exceeds

: IllegalStateException - if called for a Jakarta Persistence query language UPDATE or DELETE statement

JPA Method in jakarta.persistence.EntityManager void remove (   Object entity ) Mark a managed entity instance as removed, resulting in its deletion from the database when the persistence context is synchronized with the database. This operation cascades to every entity related by

is responsible for updating the ordering upon flushing to the database to reflect any insertion, deletion , or

will generate a constraint whose update and delete actions it determines most appropriate for the join column

instance and attempting to update or delete the state of the instance. The version attribute

JPA Method in jakarta.persistence.EntityManager void detach (   Object entity ) Evict the given managed or removed entity from the persistence context, causing the entity to become immediately detached. Unflushed changes made to the entity, if any, including deletion of the entity

: IllegalStateException - if called for a Jakarta Persistence query language UPDATE or DELETE statement

Persistence query language UPDATE or DELETE statement QueryTimeoutException - if the query execution exceeds

for a Jakarta Persistence query language UPDATE or DELETE statement QueryTimeoutException

. 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 ... .7.1_03. btc_es BTC EmbeddedSystems OK. Thanks for the update. Please note that mixing direct DELETE

__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

have inserted. I'm currently evaluating your product. So i insert and delete a lot of data. I also tried ... reference integrity and it is the application responsibility to avoid deletion from the database ... will be produced. support Support The orphan Position records are there because i deleted some Units with a DELETE

. The code looks like:    Query query = em.createQuery(" DELETE FROM DataHolder d WHERE d ... is persisting more data, the other group is deleting the first set of data via delete statements. Eventually ... the application the data sizes are larger so I guess the delete is slower and gives the appearance

the database but their classes have been deleted or missing? This is abnormal state for a database ... itself, is it correct that the objects are in the database but their classes have been deleted or missing ... of deleting classes using the Explorer, so it may be related. We cannot reproduce the exceptions

Let's say I no longer need some entity in my project and after deleting all the objects ... I found a description that the DB Explorer should be capable to delete classes? But it seems not ... of deleting classes in the Explorer. An obsolete class can be selected in the Schema / Managed

at this point is performing a delete query for all entity objects that the database contains: EntityManager em = _emf.createEntityManager(); em.getTransaction().begin(); try { Query query = em.createQuery(" DELETE FROM ExecutionGraph g"); query.executeUpdate(); query = em.createQuery(" DELETE FROM

Hi. It would be very useful to be able to delete an entire entity class from ObjectDB ... .8.2 adds support of deleting classes in the Explorer. An obsolete class can be selected in the Schema / Managed Types list and then deleted  by using [Edit Delete ] from the menu bar or right click (context menu) and Delete . support Support

with FetchType.LAZY. If I now delete a root entity using EntityManager.remove all leaf nodes will not be deleted . This only applies to the leaf nodes. If I add an additional the behaviour changes so that these new leafes will not be deleted . I created a small test case which can be downloaded at