iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
No. A successful D1 UPDATE that matches zero rows does not, by itself, fail a batch or trigger rollback. Cloudflare documents rollback when a statement fails—not when its change count is zero.
Why zero updated rows are not a batch failure
D1’s batch() method runs prepared statements sequentially and non-concurrently as one batch transaction. Cloudflare says that if a statement in the sequence fails, D1 returns an error for that statement and aborts or rolls back the sequence. A successful statement that matches no rows is not documented as a failure condition. Cloudflare’s D1 Database API documentation
The result separates whether an operation succeeded from how many rows it changed. A D1Result includes a success boolean and meta.changes count; Cloudflare’s example shows success: true alongside meta.changes: 0. Cloudflare’s D1 return objects documentation
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →How the two outcomes differ
| Case | Statement result | Batch outcome | Earlier writes |
|---|---|---|---|
Successful UPDATE matches no rows |
May report success: true and meta.changes: 0. |
Zero changes alone are not a documented rollback trigger. | Not rolled back solely because this statement changed no rows. |
| A statement produces an execution error | D1 returns an error for the failing statement. | The batch sequence aborts or rolls back. | Earlier writes in the sequence are rolled back, according to the documented batch behavior. |
Batch results correspond to prepared statements in input order, so a test can inspect the result associated with the no-match update. Cloudflare’s D1 Database API documentation
#1 Best Overall
Test zero changes separately from rollback
Use prepared statements and a deterministic fixture so the update’s WHERE clause is known not to match. Keep this check distinct from a test of statement failure.
- Set up a known fixture. Create or seed the rows needed for the test, and choose a key that is absent for the zero-match case.
- Batch the no-match update. Include the prepared
UPDATEand, if useful, another harmless statement. Ensure the update runs successfully but its predicate matches no rows. - Inspect the corresponding result. Because batch results follow input order, assert that the update’s result has
success === trueandmeta.changes === 0. - Test rollback with a real SQL error. In a separate batch, perform a write first and then execute a statement that produces a genuine SQL error.
- Verify persisted state. Assert that the failing batch reports its error and that the earlier write did not persist.
This structure tests the documented boundary: a zero-row change is a successful result, while a statement failure is the documented reason for aborting or rolling back the batch. Cloudflare documents the behavior; these steps are a test outline, not a report of a test run. Batch behavior · Result fields
When your application needs exactly one row changed
D1 does not document an automatic rule that converts meta.changes === 0 into an error. If your application requires exactly one row to change—for example, to treat a missing record as a failed operation—check the result count in application logic and explicitly handle or throw on a mismatch. That is an application-level policy, not an implicit D1 batch behavior.
Scope of the documented behavior
Cloudflare’s D1 Database API page was last updated June 22, 2026, and its Return objects page was last updated September 17, 2026. The documented contract supports sequential batch execution and rollback when a statement fails; it does not promise that every successful write affects at least one row. D1 Database API · Return objects
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
