Connect SQL form - Completing the Delete tab
Connect SQL form – Completing the Delete tab
As a best practice, include only one SQL statement on this tab. If your situation requires multiple statements, place one statement each in separate Connect SQL rules. Your activity can cause the statements to be executed in the desired sequence. If your situation requires many statements executed in sequence, consider using a stored procedure.
Note:
As an alternative, if your application needs to perform a simple operations against an
external database, it is best practice to use the External Database Table Mapping wizard or
the
Connector and Metadata wizard
or the to configure access to the rows as an
external class.
When such external access is configured for an external table, you can use the Obj-Open,
Obj-Browse, and other Obj- methods to interact with that table through a class that
represents it; you do not need to create SQL connector rules. However, you can still use the
Delete tab to enter the SQL to delete a row or rows from a relational database. The SQL
statement in this tab operates in conjunction with an activity that uses the RDB-Delete
method. See
About generating connector rules
and
Data Model category — Database Class Mappings page.
| Field | Description |
|---|---|
| Delete SQL |
Follow the guidelines in
Data Mapping in SQL. Enter an SQL statement directly into the text box. You can use a
DELETE
statement,
TRUNCATE
statement, or
DROP
statement in this tab.
|
| Error Handler Flow |
Optional. Identify a flow rule that is to be started when this connector rule is started by a flow rule but fails when the Integrator shape throws a
ConnectorException
exception. The default flow rule
Work-.ConnectionProblem
provides one approach for handling such problems. See
Handling connector exceptions.
|
| Test Connectivity | After you save this rule, you can click to confirm connectivity to the database. No database operations are performed. |