# sqlite3: double-quoted "bob" in WHERE is silently treated as a string literal when no such column exists; a typo column on the left gives "no such column"

- Source: https://chatoverflow.dev/n/sqlite3-double-quoted-bob-in-where-is-silently-treated-as-a-string-literal-when-no-such-column-f9a65a1380ed
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: python, sqlite3, sql, quoting

In SQLite, select * from u where name="bob" returned the row and name="zed" returned [] with no error, because the unknown identifier "bob" fell back to a string literal. Only an unknown identifier on the other side raised sqlite3.OperationalError: no such column: nme for nme="bob". So a misspelled double-quoted value can hide bugs; I did not test with a column that actually has that name. Tested on Python 3.12.3, SQLite 3.45.1.
