ObjectDB Database Search

Jakarta Persistence (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 Returns: the query object. Since: Jakarta Persistence (JPA) 2.1

when a database is opened and deletes it when the database is closed. The recovery file name ... tests. The content of these temporary databases is deleted when you use the drop URL connection

for deletion , and so on. Query results are not limited to entities. You can use almost any valid JPQL ... to update and delete , which require managed entities. Managed entities can, however, be returned from

is marked for removal (when remove() is called). @PostRemove : Invoked after an entity is deleted from

., for update or delete . If the query is not an update or delete query, query execution will result in ... an instance of Query for executing a criteria delete query. Parameters: deleteQuery - a criteria delete query object Returns: the new query instance. Throws: IllegalArgumentException - if the delete query

the database when the transaction is committed (unless it is being deleted before commit). An attempt ... the object exists in the database. If an object is deleted from the database, its unique ID is never used ... is not deleted from the database, just its name is removed. Objects with names are called root objects

Using version 2.7.4_01, we did a repair. After repair a former link to a missing reference was converted to null. This cannot be deleted using explorer   hgzwicker Hans-Georg Zwicker Thank you for this report. Build 2.7.4_02 fixes the issue. support Support

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaBuilder CriteriaUpdate createCriteriaUpdate (    Class targetEntity ) Create a CriteriaUpdate query object to perform a bulk update operation. Parameters: targetEntity - target type for update operation Returns: the query object. Since: Jakarta Persistence (JPA) 2.1

: FOREIGN KEY ( {, } ... ) REFERENCES [ ( {, } ... ) ] [ ON UPDATE ] [ ON DELETE ... will generate foreign key constraints whose update and delete actions it determines most appropriate ... element is not specified, the provider will generate a constraint whose update and delete actions

T2 then modifies or deletes that row, before T1 has committed. Both transactions eventually commit ... then modifies or deletes that row, before T1 has committed or rolled back. A lock with LockModeType

.   My situation is where many clients from 1 company are accessing the same counter when bulk

.getResultList(JpaQuery.java:719) at schemaupdate. delete .UpdateDB.main(UpdateDB.java:32) Exception in thread ... ) at schemaupdate. delete .UpdateDB.main(UpdateDB.java:32) btc_es BTC EmbeddedSystems Thank

Hello, we can't understand why the performance of queries is not the best and the execution requires so much memory. In the implementation of our UnitTests we have used " DELETE FROM Object" to delete the database. That did not work because we often get an "out of memory" exception

Hi, I have deleted an instance of ClassA . However, if I try to access ClassB , which has a field of type ClassA , ClassB.classA , then, rather than getting a null pointer for classB.classA , I ... are removed/ deleted from the databases - it is the application responsibility to clear any references

; em.createQuery(" delete from Street s").executeUpdate();         em.createQuery(" delete from Location l").executeUpdate();        

responsibility to prevent broken references. When an OtherEntity object is deleted the application

for all of those. So i'm still a bit confused on why this file lingers and why I can't delete it without waiting

java I assume that if I'll back up the .odb file, delete it and then restore it will fix the issue

database. support Support Looking through the code, there is no other 'point' declared. I deleted the db

server because Netbeans kept deleting my database each time I deployed with stand-alone mode

the collection and not delete any of the Readings from the DB. Also, refreshing or reading

indicates that the database is not corrupted. The two missing objects are probably the result of deleting

.ObjectdbTest.main(ObjectdbTest.java:42) sjzlondon Steve Zara There was a bug in handling JDO delete

;  odbFile. delete ();         EntityManagerFactory emf

and delete database objects. Chapter 7 - JDOQL Queries Describes JDOQL, the JDO Query Language. The last

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

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 

.ObjectCacheDB.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

Hi, When deleting an entity "Mitglied" - everything works fine. Trying to delete another one (in a separate transaction) always causes a NullPointer Exception in __odbGetNumMember line 1 of the enhanced Mitglied class. I am unable to replicate it in a simple testcase but it always happens in

and the os allowed us to delete the files in question without any problem. In this case we weren't ... ? support Support It was repeatable at the time but we ended up deleting the odb$ to get the app started

navigation through a broken reference (probably a reference to a deleted object) during query execution

Fixed an exception due to to an unused type referencing a deleted type.