SQLite

File-based database: run SQL, insert and delete rows, read table definitions, and back up

Signs in with: Connection details
Runs on: Cloud or On-Prem Worker
Operations: 23
Ready-made triggers: 0

Connect SQLite

In Neblex open Connect › Connections and click New Connection.
Search for SQLite and give the connection a clear name.
Fill in the fields. Secret values are encrypted and never shown again.
Click Test, then Create Connection.

If the system is only reachable inside your network, choose an On-Prem Worker under Test from and run the flow on that Worker. See On-Prem Workers.

Field	What to enter
Database fileRequired	The full path of the SQLite database file on the machine where the On-Prem Worker runs.Example: `/var/lib/app/data.db`
Open read-onlyOptional	Open the file for reading only, so no step using this connection can change it.
Create the file if it does not existOptional	Create an empty SQLite database at this path when no file exists yet. Leave off to report a missing file instead.
Enforce foreign keysOptional	Check FOREIGN KEY constraints on every write, as most applications that use SQLite expect.

Use it in a flow

Open a flow, open the node library and search for SQLite.
Drag it onto the canvas and choose an Operation and your connection.
Map the operation's fields from earlier steps, or click Map with Matt.
Use Test this step to see what it returns, then save.

To start a flow from SQLite without a ready-made trigger: a Poll for changes trigger on SQLite with your own query passes on new or changed records.

Operations

23 operations in 3 groups. Each one is a step you can add to a flow.

Database8

Back up to a file`backupTo`		Write a consistent copy of the database to a new file on the On-Prem Worker's machine.
Check database integrity`integrityCheck`		Run SQLite's quick integrity check; a healthy database returns one row reading ok.
Compact the database`vacuum`		Rebuild the database file to reclaim free pages.
Get current time`serverTime`		Return the current UTC time as SQLite reports it.
Get database information`databaseInfo`		Return the page size, page count, file size, free pages, text encoding, journal mode, user version and application id of the database.
Get engine version`serverVersion`		Return the version and source id of the SQLite engine that opens the file.
List attached databases`listDatabases`		List the main database, the temporary database and every attached database with its file.
Update query statistics`analyze`		Gather the table and index statistics the query planner uses.

Schema6

Get table definition`getTableDefinition`		Return the CREATE statements of a table and of its indexes and triggers.
List foreign keys`listForeignKeys`		List the foreign keys of a table with the referenced table and columns and their update and delete actions.
List table columns`listColumns`		List the columns of a table with their declared type, nullability, default and primary key position.
List table indexes`listIndexes`		List the indexes of a table with their uniqueness, origin and indexed columns in order.
List tables`listTables`		List tables and views with their schema, type and column count.
List triggers`listTriggers`		List triggers with their table and definition, optionally for one table, page by page.

SQL9

Delete rows (mapped)`delete`		Delete the row matching the key columns of each record.
Execute command`command`		Execute the SQLite INSERT, UPDATE, DELETE, DDL or PRAGMA statement entered in the statement editor.
Execute query`query`		Execute the SQLite query entered in the statement editor with bound :name parameters.
Insert rows (mapped)`insert`		Insert one row per record into a table you pick, mapping each column from the record.
Run SQL script`script`		Run several SQLite statements separated by semicolons, in order and in one transaction, with bound :name parameters.
Select rows (mapped)`select`		Read rows from a table you pick: choose the columns to return, filter by the column values you map, order and limit.
Test SQLite`ping`		Open the database file, confirm it is a SQLite database and return ok=1.
Update rows (mapped)`update`		Update the row matching the key columns of each record, setting the other mapped columns.
Upsert rows (mapped)`upsert`		Insert one row per record, or update the existing row when the key columns already match.