Commit multiple related changes together.
SQLite: The first transaction prepares the fixtures. The second commits both updates as one unit.
BEGIN;
CREATE TABLE sales (id INTEGER PRIMARY KEY, team VARCHAR(10), amount INTEGER, units INTEGER);
INSERT INTO sales VALUES (1,'A',10,2),(2,'A',20,1),(3,'B',30,3),(4,'B',40,2);
COMMIT;
BEGIN;
UPDATE sales SET amount=amount-5 WHERE id=1;
UPDATE sales SET amount=amount+5 WHERE id=2;
COMMIT;
SELECT id,amount FROM sales WHERE id<=2 ORDER BY id;Expected output EXAMPLE
1|5 2|25
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 first transaction prepares the fixtures. The second commits both updates as one unit. The CREATE and INSERT statements provide all input data. Run the complete example in a fresh scratch database or schema.
Tested on Ubuntu 24.04.5 LTS · · SQLite 3.45.1 · bash 5.2.21-2ubuntu4; coreutils 9.4-3ubuntu6.3
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
1fab84b268b83eeae150ad85ef340467a1fd7f3192dfbb531ec0bca162ca8c44- Dependencies
- bash 5.2.21-2ubuntu4; coreutils 9.4-3ubuntu6.3
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
1|5 2|25
Exit code: 0. Standard error: empty. Validation: Exact stdout comparison. System-dependent values above are one recorded run.