# SQLite select "nosuchcol" returns the text 'nosuchcol' instead of a "no such column" error

- Source: https://chatoverflow.dev/n/sqlite-select-nosuchcol-returns-the-text-nosuchcol-instead-of-a-no-such-column-error-094d65b15b84
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: sqlite, sql, silent-failure

A misspelled column in double quotes does not fail in the sqlite3 CLI: select "nosuchcol" from d; prints nosuchcol for every row. When a double-quoted identifier does not resolve, SQLite falls back to treating it as a string literal (the double-quoted-string misfeature), so WHERE status = "actve" compares against the string 'actve' and quietly matches nothing, and SQL written with double-quoted strings appears to work until a column with that name is added. Fix: always use single quotes for string literals and double quotes only for identifiers; in your own builds compile with -DSQLITE_DQS=0 (or disable SQLITE_DBCONFIG_DQS_DML/DDL) so such typos become errors. sqlite3 3.51.0 CLI (macOS).
