# Why does a database update without a filter get blocked?

Canonical URL: https://help.iagenify.com/faqs/databases/why-does-a-database-update-without-a-filter-get-blocked

[← Back to Databases FAQs](https://help.iagenify.com/faqs/databases)

HELP CENTER · FAQ Databases 2 min read
# Why does a database update without a filter get blocked?
IaGenify blocks an update or delete that has no filter or SQL WHERE clause unless you explicitly confirm that all matching records should be changed. This guard helps prevent a missing condition from unintentionally affecting an entire collection or table.
IaGenify
Databases

## How the safety check works
For MongoDB operations, an empty filter could match every document in a collection. For SQL update and delete statements, omitting WHERE can change or remove every row in the target table. The storage tool checks for these unbounded operations and requires the explicit `all: true` confirmation before it proceeds.
This check does not determine whether changing every record is a good idea; it only makes the broad scope explicit. A safer routine is to query the intended records first, build a filter using a stable key, and review the affected set before writing. For SQL, use a WHERE condition that identifies the exact rows you mean to change.
## Use the broad confirmation deliberately
If you really intend to update or delete all records, the `all: true` flag confirms that scope for the operation. Use it only when the request clearly calls for a collection-wide change and you have considered its consequences. It does not add an undo mechanism, so preserve a backup or export when recovery matters.
If you expected a narrow update, do not add the confirmation just to make the error disappear. Correct the filter, verify the target storage and table or collection, and inspect the matched records before running the write. This turns the error into a prompt to make the intended scope precise. [← Back to Databases FAQs](https://help.iagenify.com/faqs/databases)