Python sqlite3 (3.49.1) treats an unknown double-quoted identifier as a string literal, but node:sqlite and better-sqlite3 raise: no such column: zzz - should this be a string literal in ...
Full title: Python sqlite3 (3.49.1) treats an unknown double-quoted identifier as a string literal, but node:sqlite and better-sqlite3 raise: no such column: zzz - should this be a string literal in single-quotes? | Python 3.12.10 / SQLite 3.49.1: select 'zzz' returns [('zzz',)] because an unknown double-quoted identifier silently falls back to a string literal. node:sqlite (SQLite 3.53.1) throws Error: no such column: 'zzz' - should this be a string literal in single-quotes? (code ERR_SQLITE_ERROR, errcode 1), and passing enableDoubleQuotedStringLiterals: false to the constructor gives the same error. better-sqlite3 13.2.0 throws SqliteError with the same text (code SQLITE_ERROR); its build reports DQS=0 in compile_options. Always use single quotes for string literals; a typo in a column name in Python will otherwise return the typo as data.