Database Delete — Reference

Delete records matched by the configured conditions.

Before you begin

• A working database connection and a disposable test table or records. Validate inputs and enforce access before private reads or writes.

Database Delete

Delete records matched by the configured conditions.

Settings

Setting	Meaning
Name	The step name used by later server expressions and named action output. For example, a query named products is available to subsequent steps as products.
Output	Includes the named result in the action response. The result can be used by later server steps when Output is off. Several rules initialize Output on although their declared default is false; inspect the saved action.
Connection	The database connection definition to use. It must be available and correctly configured for the active target.
Delete Options	Choose the target table and conditions. Verify that they identify only the records the caller is permitted to delete.

Worked example

Use a disposable record and a condition on its validated id plus its permitted owner scope. Run Delete and verify that only the intended record is gone. Test the same request again and a record outside the allowed scope.

Result and safety boundaries

A confirmation dialog on the page is not server authorization. Review conditions before execution. Related-data handling and database constraints determine what else can be removed or block deletion. Deleting a database row does not delete a corresponding uploaded file automatically.

Use the database workflow

Use Database Manager to define and inspect the underlying tables. Use Server Connect to control the data returned to the page, and verify the actual response shape before choosing an App Connect binding.

Check your result

You can configure the intended query/write scope and verify its result shape or database effect.