SQL and relational

SQLite

SQLite is treated as a local-file workbench with file posture, PRAGMA health, integrity checks, guarded VACUUM INTO, and table import/export.

Available12 minDesktop

Prerequisites

Install the current DataPad++ desktop pre-release on Windows, macOS, or Linux.
Have the endpoint, database file, or cloud account details for a SQLite datastore you are authorized to use. Start with least-privileged, read-only access.
Keep an independent backup before enabling edits, administration, restore, or transfer execution.

Connect and run a safe query

1
Create the connection
Open Library, choose Create connection, and select SQLite and a supported Connection method tab.
2
Test and save
Complete the applicable fields and enable Read-only connection. Test connection when available; new local files and pending secondary credential changes must be saved first. Review runtime limitations and warnings.
SQLite connection setup. The SQLite connection dialog with supported method tabs and illustrative, non-secret settings. Expand optional sections and review runtime limitations before saving. Open full size
3
Open the native explorer
Use Save Connection, or Create Database and Save Connection for a new local file, then open the SQLite Explorer where supported.
4
Select a scope
Select the database / schema scope that should be attached to the new tab.
5
Run a bounded read
Open a query tab, paste the bounded read-only sample below, and choose Run or press Ctrl/Cmd+Enter.
SQLite native workflow. A representative SQLite explorer and bounded read-only workflow. Replace the example objects with names from your datastore. Open full size
6
Inspect the result
Inspect Results, Messages, History, and Details; dock the panel on the bottom or right as needed.
7
Export when needed
Export only the required rows after reviewing format, destination, and redaction options.
8
Open diagnostics or transfers
Open Diagnostics or Transfers from the drawer/status bar and treat disabled reasons as capability boundaries, not transient errors.

Connection fields

Field	Required	Purpose	Safe example
Name	Yes	A clear profile name, without credentials.	SQLite development
Connection method	Yes	Choose a supported tab. The fields below apply only to the selected method and deployment.	Local database file / Connection string
Environment	No	Attach the intended variable and safety context.	Local development
Read-only connection	No	Enable for initial exploration. This does not make pre-release software safe for production workloads.	Enabled
Database file	Yes	Open an existing file, or choose a folder and filename under Create new database. Creation occurs only on final save.	example.sqlite
Complete connection string	Yes	Required in Connection string mode only. Saved unchanged as one vault secret with Save Connection. Blank keeps an existing stored value.	Paste your complete provider string; do not share it
Open mode	No	General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	read-write / read-only / uri
Busy timeout (ms)	No	Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default
Journal mode	No	Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	delete / truncate / persist / memory / wal / off
Synchronous mode	No	Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	off / normal / full / extra
Cache size	No	Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default
Foreign keys	No	Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default
Recursive triggers	No	Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default
Immutable file	No	Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	Driver default
Temporary storage	No	Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.	default / file / memory

Run the sample query

SQLite read-only example

SELECT id, name, status
FROM customers
ORDER BY id
LIMIT 25;

Explore and inspect

Browse attached databases, schemas, tables, views, columns, indexes, triggers, generated columns, virtual tables, and PRAGMA health panels.
Inspect table grids, raw payloads, PRAGMA results, integrity-check messages, and primary-key row edit evidence when the table target is complete.

Diagnose, administer, and transfer

Review file posture, attached databases, indexes, triggers, virtual tables, generated columns, PRAGMA health, and integrity-check status.
Preview check, analyze, optimize, vacuum, reindex, local file backup, and table import/export operations with file and environment guardrails.
Import — Live. SQLite transfers rows into an existing table. Formats: CSV (portable-lossy), JSON (portable), NDJSON (portable). Destinations: local file.
Export — Live. SQLite transfers rows into an existing table. Formats: CSV (portable-lossy), JSON (portable), NDJSON (portable). Destinations: local file.
Backup — Live. SQLite creates a complete local database snapshot. Formats: SQLite database (native). Destinations: local file.
Restore — Live. SQLite creates a complete local database snapshot. Formats: SQLite database (native). Destinations: local file.

Transfers Center. Transfers Center shows a failed example transfer with its warning count, failure detail, retry control, and dismiss action. — **Transfers Center.** Transfers Center shows a failed example transfer with its warning count, failure detail, retry control, and dismiss action. Open full size

Capabilities and availability

Capability	Status	Notes
Native explorer	Available	Browse attached databases, schemas, tables, views, columns, indexes, triggers, generated columns, virtual tables, and PRAGMA health panels.
Read queries	Available	Run raw SQLite SQL, table SELECT builders, PRAGMA helpers, integrity-check helpers, and focused local-file metadata queries.
Inline editing	Guarded	Requires key evidence, a writable profile, and environment confirmation.
Diagnostics / administration	Guarded	Preview check, analyze, optimize, vacuum, reindex, local file backup, and table import/export operations with file and environment guardrails.
Import / export / transfer	Guarded	Availability follows the authoritative runtime transfer manifest and shows a disabled reason when execution is not implemented.

Safety and limitations

Troubleshooting

Symptom	Resolution
Test connection fails or times out	Verify endpoint, port, TLS mode, proxy settings, service health, firewall rules, and network access. Keep the profile unsaved until the test explains the failure.
Explorer branches are empty or disabled	Confirm the selected database / schema, refresh the branch, and grant the minimum metadata permissions described in the connection warning.
Run, edit, admin, or transfer is disabled	Read the visible disabled reason. Select a compatible target, turn off read-only only when authorized, or use the documented preview/export fallback.
The sample query fails or returns different columns	Replace the example names with objects from your SQLite datastore, confirm the selected database / schema, and keep the query bounded while you validate the result.

Prerequisites

Create the connection

Test and save

Open the native explorer

Select a scope

Run a bounded read

Inspect the result

Export when needed

Open diagnostics or transfers