Database Connection — Reference
Choose and configure the server database connection used by query and write actions.
Choose and configure the server database connection used by query and write actions.
Before you begin
Section titled “Before you begin”- A supported database server or file and connection details for the intended development target.
A reusable server connection
Section titled “A reusable server connection”A Database Connection identifies the driver and connection settings used by server actions. It does not create tables or fetch records by itself. Its controls depend on whether you are editing a connection definition or selecting an existing one.
Context-dependent controls
Section titled “Context-dependent controls”| Control | Meaning |
|---|---|
| Name | While editing a connection module, names the reusable definition. In an ordinary action the selector loads an existing definition instead of exposing every credential field. |
| Connection Options | Opens the database connection editor appropriate to the server model. Configure the driver, database/host or database-file path and credentials required by that driver. SSL, pool and schema/search-path options depend on the selected driver and target. |
| Timezone Handling | Available in the Node.js definition editor: Driver dependent, Local or UTC. It affects how returned date/time values are handled, not the original database schema. Check date-only values, timestamps with and without time zones, and the page’s expected formatting before changing it. |
Verify a development connection
Section titled “Verify a development connection”Create or open the intended development connection in Database Manager, save its settings and test connectivity. In a Server Connect query select that definition and fetch a small known table. Confirm the expected fields and one known date/time value. Repeat this check for another deployment target instead of assuming the same host and credentials apply.
Keep configuration and data access separate
Section titled “Keep configuration and data access separate”Database credentials belong on the server. A connection does not authorize an incoming user to read every table; restrict actions and record scope separately. A successful connection test does not prove that a query, write permission or production target is correct.
Configure a query
Section titled “Configure a query”After verifying the connection, choose the appropriate ordinary, single-record or paged query and inspect its output shape.
Check your result
Section titled “Check your result”You can distinguish a saved connection definition from a query step, select it for the active target, and verify connectivity and returned date handling.