Skip to content

fix: raise NoTable from rows_where() and delete_where() for non-existent tables - #850

Open
ikatyal2110 wants to merge 1 commit into
simonw:mainfrom
ikatyal2110:fix-rows-delete-nonexistent-table
Open

fix: raise NoTable from rows_where() and delete_where() for non-existent tables#850
ikatyal2110 wants to merge 1 commit into
simonw:mainfrom
ikatyal2110:fix-rows-delete-nonexistent-table

Conversation

@ikatyal2110

@ikatyal2110 ikatyal2110 commented Aug 29, 2026

Copy link
Copy Markdown
Contributor

rows_where() silently returned an empty iterator and delete_where() silently returned self when called on a table that does not exist, masking bugs in callers that passed a wrong table name. Both methods now raise NoTable, matching the behaviour of count_where() and duplicate(), as described in issue #841 as the intended v5 behaviour. Fixes #841


📚 Documentation preview 📚: https://sqlite-utils--850.org.readthedocs.build/en/850/

…ent tables

rows_where() silently returned an empty iterator and delete_where()
silently returned self when called on a table that does not exist.
This masked bugs in callers that passed a wrong table name.  Both
methods now raise NoTable (matching the behaviour of count_where()
and duplicate()), as planned for the v5 release.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

rows_where() and delete_where() fail to throw errors against non-existent tables (fix in v5)

2 participants