IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > JDBC > Overview of IBM WebSphere Adapter for JDBC > Technical overview > Outbound processing > Outbound operations
Delete operation
The Delete operation is performed by pruning the incoming business object and then retrieving the complete business object from the database. The Delete operation is then applied recursively on each business object in the hierarchy.
The Delete operation supports physical and logical deletes, depending on the StatusColumnName value in the application-specific information of the business object. If the StatusColumnName value is defined, the adapter performs a logical delete operation. If the StatusColumnName value is not defined, the adapter performs a physical delete operation.
Physical deletesFor physical deletes, the adapter takes the following actions:
- Deletes all multiple-cardinality child business objects, recursively.
- Deletes the top-level business object.
If the top-level business object is a wrapper object, it is ignored. No delete is done for wrapper business objects.
- Deletes all single-cardinality child business objects contained with ownership, recursively.
Logical deletesFor logical deletes the adapter takes the following actions:
- Issues an update that sets the status attribute of the business object to the value specified by the business object-level application-specific information. The adapter ensures that only one database row is updated as a result, and it returns an error if this is not the case.
- Deletes all single-cardinality children contained with ownership and all multiple-cardinality children, recursively and logically. The adapter does not delete single-cardinality children contained without ownership.
NULL data and the Delete operationThe adapter can delete a record from a database table when the column value is null.
For example, a Customer business object might have these columns: custid, ccode, fname, and lname, where custid and ccode form composite keys. Composite keys are primary keys that refer to more than one attribute and are used to define the uniqueness of the business object. You can delete a Customer record for which ccode is null. The adapter generates a delete query for the Delete operation as:
delete from customer where custid=? and ccode is nullFor more information about null data, see Null Data - Frequently Asked Questions.
Related concepts:
Related reference: