Internal Website Search

I have a entity class named Agent having fields Id,Name,Code,Skill ...etc. I wants to delete only the Skill from a row so I use Query like " Delete a.Skill from Agent a where a.Id = 112" but It gives ... Manoj Kumar Maharana DELETE queries are for deleting complete objects (rows). You may use an UPDATE

Is there a configuration parameter to set this? dmoshal David Moshal You can set cascade delete using annotations (see also the Orphan Removal section). JDO defines similar annotations, and both JPA ... configuration. You cannot set global cascade delete since that will be too risky - you may delete the entire database. support Support

Hi! I was looking for ways to delete a class (entity/embedded) from a database through Explorer ... is to delete the whole db and make a new one, but that's not a good scenario ... . However, it only affects the list of classes in the Explorer, so you may just ignore the deleted class

    Suppose entity A is referenced from entity B, like (A - * B) but not actually having that reference, instead only B has @ManyToOne relationship to A and A has none. Is there a way to cascade delete of B's when deleting A? Or this should be done programatically with separate

    Hello , is it possible to get disk usage of database ? If disk usage becomes too high , delete old date files from database. And recalculate disk usage back ?   kadirbasol Kadir ... usage and delete some old files" and should be focus only on that subject. support Support

simple codes(see attachment), failed.   gzdillon Lai Yang DELETE queries should not be run with getSingleResult ( which is for SELECT queries). Use executeUpdate instead. See this manual page . support Support

;   private Set timeslots = new HashSet(); And i would like to delete the timeslots

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

My JDO application does inserts with binds, and then subsequently does bulk deletes using this code: pm.currentTransaction().begin(); Extent extent = pm.getExtent(ABC.class, true); Query q = pm ... (bookmarks). Instead of the above code, I could iterate over the Extent and delete the entities

of Address which cascades deletes (orphanRemoval=true) to its children which is what we want ... it has never been deleted from the collection (at least, until the transaction is comitted ... Entities within the collection of a Contact when we delete the Contact? Is that cascaded or do we need

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

after the crash we cannot delete specific objects, see screenshots of explorer. Database will be soon available (size 5.561.119 KB) on hummingbird-systems.com, user/pw your db name, main menu option objectdb  hgzwicker Hans-Georg Zwicker meanwhile the database became completely unusable

accidently we used the option delete on a collection of type ArrayList . On doing so the type changed to List . we are using explorer version 2.7.1_02 How can we change that back again ? hgzwicker Hans-Georg Zwicker Is it only an issue with the type of the field as shown by the Explorer or

JPA Method in javax.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 Return: the query object Since: JPA 2.1

. Public Methods int executeUpdate () Execute an update or delete statement. Return: the number of entities updated or deleted Throws: IllegalStateException - if called for a Java Persistence query ... UPDATE or DELETE statement QueryTimeoutException - if the query execution exceeds the query timeout

() Execute an update or delete statement. Return: the number of entities updated or deleted Throws ... : IllegalStateException - if called for a Java Persistence query language UPDATE or DELETE statement ... DELETE statement QueryTimeoutException - if the query execution exceeds the query timeout value set

, e.g., for update or delete . If the query is not an update or delete query, query execution ... ;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

that is common to both top-level criteria queries and subqueries as well as to update and delete ... queries and criteria update and delete operations are typed differently. Criteria queries are typed according to the query result type. Update and delete operations are typed according to the target

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

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

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

 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

.  Based on the implementation, you will need to delete the odb file between each execution ... . Persisting bulk of objects every transaction (instead of a transaction per entity object). support

JPA Method in javax.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 javax.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

. Another transaction T2 then modifies or deletes that row, before T1 has committed. Both transactions eventually commit ... reads a row. Another transaction T2 then modifies or deletes that row, before T1 has committed or

.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

semicolons. Since: JDO 1.0 long deletePersistentAll () Deletes all the instances of the candidate class that pass the filter. Returns the number of instances of the candidate class that were deleted ... if deletePersistent were called on them. Specifically, if the class of deleted instances implements

JDO Method in javax.jdo.Query long deletePersistentAll () Deletes all the instances ... that were deleted , specifically not including the number of dependent and embedded instances. Dirty instances ... changes as if deletePersistent were called on them. Specifically, if the class of deleted instances

is implemented by listeners to be notified of delete events. Since: JDO 2.0 Public Methods void postDelete ( InstanceLifecycleEvent  event) Invoked whenever a persistent instance is deleted ... after the instance transitions to persistent- deleted . Access to field values is not permitted. Parameters: event

;pc) Delete the persistent instance from the data store. This method must be called in an active ... the closure of the instance persistent, the closure of the instance is not deleted from the data store. This method has no effect if the instance is already deleted in the current transaction. This method

, transactional, dirty, new, deleted , or detached; and to get its associated PersistenceManager ... has been deleted . Instances that have been deleted in the current transaction return true. Transient instances return false. Return: true if this instance was deleted in the current transaction

whether the instance is persistent, transactional, dirty, new, deleted , or detached ... has been deleted . Instances that have been deleted in the current transaction return true ... . Parameters: pc - the PersistenceCapable instance. Return: true if the parameter instance was deleted in

isDeleted (Object pc) Tests whether the parameter instance has been deleted . Instances that have been deleted in the current transaction return Boolean.TRUE . Instances known by the implementation to be non- deleted return Boolean.FALSE . Instances not recognized by the implementation return null

whether this object has been deleted . Instances that have been deleted in the current transaction return true ... : true if this instance was deleted in the current transaction. See Also: PersistenceManager ... whether this object is dirty. Instances that have been modified, deleted , or newly made persistent in the current

JDO Interface DeleteCallback This interface is used to notify instances of delete events. Since: JDO 2.0 Public Methods void jdoPreDelete () Called before the instance is deleted . This method is called before the state transition to persistent- deleted or persistent-new- deleted . Access to field

) Tests whether the parameter instance has been deleted . Instances that have been deleted in the current transaction return Boolean.TRUE . Instances known by the implementation to be non- deleted return ... - the instance. Return: Boolean.TRUE if the parameter instance was deleted in the current transaction

ForeignKeyAction deleteAction default ForeignKeyAction.UNSPECIFIED Delete action to apply to any foreign key ... (and will be deleted when the owner is deleted ). Since: JDO 2.1 String embedded default

deleteAction default ForeignKeyAction.UNSPECIFIED Delete action to apply to the foreign key for the key ... (and will be deleted when the owner is deleted ). Since: JDO 2.1 String embedded default "" Whether this key

JDO Method in javax.jdo.spi.StateManager boolean isDeleted (   PersistenceCapable pc ) Tests whether this object has been deleted . Instances that have been deleted in the current ... PersistenceCapable instance Return: true if this instance was deleted in the current transaction. See Also: PersistenceManager.deletePersistent (Object pc) Since: JDO 1.0

JDO Static Method in javax.jdo.JDOHelper boolean isDeleted (   Object pc ) Tests whether the parameter instance has been deleted . Instances that have been deleted in the current ... if the parameter instance was deleted in the current transaction. See Also: PersistenceManager.deletePersistent (Object pc) PersistenceCapable() Since: JDO 1.0

JDO Method in javax.jdo.listener.DeleteLifecycleListener void postDelete (    InstanceLifecycleEvent  event ) Invoked whenever a persistent instance is deleted , for example ... to persistent- deleted . Access to field values is not permitted. Parameters: event - the delete event. Since: JDO 2.0

JDO Method in javax.jdo.listener.DeleteCallback void jdoPreDelete () Called before the instance is deleted . This method is called before the state transition to persistent- deleted or persistent-new- deleted . Access to field values within this call are valid. Access to field values

) Delete the persistent instance from the data store. This method must be called in an active ... of the instance persistent, the closure of the instance is not deleted from the data store. This method has no effect if the instance is already deleted in the current transaction. This method throws

. Since: JDO 2.1 ForeignKeyAction deleteAction default ForeignKeyAction.UNSPECIFIED Delete action to apply ... is dependent on the owner, and will be deleted when the owner is deleted . Since: JDO 2.1 String

Since: JDO 2.0 void jdoPreDelete () Called before the instance is deleted . This method is called before the state transition to persistent- deleted or persistent-new- deleted . Access to field values

JDO Method in javax.jdo.spi.PersistenceCapable boolean jdoIsDeleted () Tests whether this object has been deleted . Instances that have been deleted in the current transaction return true. Transient instances return false. Return: true if this instance was deleted in the current transaction

JDO Annotation Attribute in javax.jdo.annotations.Persistent String dependent default "" Whether related object(s) of this member are dependent and so deleted when this object is deleted . Since: JDO 2.1

dependent default "" Whether related object(s) of this member are dependent and so deleted when this object is deleted . Since: JDO 2.1 String dependentElement default "" Whether the elements of this member

JDO Annotation Attribute in javax.jdo.annotations.Key String dependent default "" Whether the key is dependent on the owner (and will be deleted when the owner is deleted ). Since: JDO 2.1