Edit rows with primary-key protection
Open a database and select a table. When the table has a usable primary key, the result includes actions for editing and deleting individual rows. The editor uses the primary-key values to target the intended row instead of relying on its visual position.
- Choose Edit on the row.
- Change the required field values. Use the null option when the column permits it.
- Save the row and confirm the updated result.
- Choose Save DB to download the database when finished.
Use SQL for bulk changes
The query workspace also supports SQLite write statements. For example:
UPDATE "products" SET "active" = 0 WHERE "last_order_at" < '2025-01-01';
Review the WHERE condition carefully before executing an update or delete. A good workflow is to run the same condition as a SELECT first, confirm the affected rows, and only then execute the write query.
What can prevent row editing?
Safe row actions require the viewer to identify records reliably. Tables without primary keys may be shown as read-only in the row interface. Views, computed results, joins and aggregate queries generally cannot be mapped safely back to one source row, although you can still inspect or export them.
Download the finished database
The Save DB action exports the current SQLite database state, including successful row edits and write queries. Keep the original as a backup until you have tested the downloaded file in the application that uses it.