Connect SQL form
Completing the Delete tab
|
|
Alternative: Starting in V5.3, if
your application needs to perform a simple save operation against an
external database, it is best practice to use the Connector and Metadata
Accelerator 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. See About
generating 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.
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.
STEWS TN 8/22/02 If your situation requires many statements
executed in sequence, consider using a stored procedure.
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 |
| Error Handler Flow |
|
| Test Connectivity |
C-605 After you save this rule, you can click to confirm connectivity to the database. No database operations are performed. |
C-1075
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 task throws a