Database Update — Reference

Update only the database records selected by its 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 Update

Update only the database records selected by its 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.
Update Options	Choose writable columns and conditions that identify the permitted records. These conditions determine the update scope.

Worked example

Create a disposable product, then update its price using a condition on its id and the authenticated owner where applicable. Verify the stored row and affected result. Test a missing id and an id the caller does not own.

Result and safety boundaries

A missing or overly broad condition can update many records. Map only intended columns; do not pass a complete untrusted request object as every writable value. An affected count of zero can mean no matching record or no effective change depending on the driver; inspect the actual row when that distinction matters.

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.