Update a row on conflict.
Use a primary key to insert or update one value.
CREATE TABLE settings (key TEXT PRIMARY KEY, value TEXT);
INSERT INTO settings VALUES ('theme','light');
INSERT INTO settings VALUES ('theme','dark') ON CONFLICT(key) DO UPDATE SET value=excluded.value;
SELECT key, value FROM settings;Expected output EXAMPLE
theme|dark
Details
Requires SQLite 3.40 or later. Run with sqlite3 demo.db in a scratch directory. Result rows below use | between columns, without headers; client display formatting may differ. The conflict target must match a uniqueness constraint. The verifier uses a fresh SQLite file for each example.
Tested on Ubuntu 24.04.5 LTS · · SQLite 3.45.1 · sqlite3 3.45.1-1ubuntu2.8
Test inputs, results and environment
The exact published code ran in a dedicated Linux test container with prepared inputs. Snippet process uid 65534 with a read-only root filesystem and temporary working files. Networking disabled. Fixtures and output records are isolated from the application database. Testing covers this example and its stated checks, not every input, operating system, or runtime version. The Linux container shares its host's kernel; this is not a native Windows test.
- Architecture / host kernel
- x86_64 / 6.18.54.1-microsoft-standard-WSL2
- Snippet identity / locale
- uid=65534, gid=65534 (unprivileged process) / C.UTF-8
- Interpreter invocation
Execute the exact SQL in a fresh database/schema; serialize result rows with | separators- Container image ID
sha256:ec91410a8f6ec3e985830b5e3a0560306d36f8c1c5ccd91a6699abe707123fa3- Code SHA-256
06619c9413f96813a62c2ddb2be416391269b09eb2a943dc6921480c83e6702f- Dependencies
- sqlite3 3.45.1-1ubuntu2.8
Test input setup
These are the prepared inputs used by the test harness. See Details above for the prerequisites and how to run this example.
# No input files required.
Observed standard output
theme|dark
Exit code: 0. Standard error: empty. Validation: Exact stdout comparison. System-dependent values above are one recorded run.