It appears that SQLite, apparently as a "compatibility feature", parses double quoted identifiers as string literals if no matching column is found.

I understand that it does so for people who write improper sql, and for backwards compatibility with legacy projects created by such people, but it makes debugging very difficult for those of us writing proper sql on brand new projects.

For example,

```
SELECT * FROM "users" WHERE "usernme" = 'joe';

```

returns a query with 0 rows, since the string 'usernme' does not equal the string 'joe'.

This leaves me scratching my head wondering why i'm not getting joe's row even when i know there's a user by that name until I painstakingly backtrack my code and realize that I left out an a.

Is there any "strict mode" PRAGMA or API option to enforce quoting rules and treat all double-quoted strings as identifiers so that it will inform me immediately if one is misspelled?

(And please, no answers telling me not to quote identifiers if I don't need to, because any such answer is basically telling me that in order to get proper debugging, you have to write bad code in the first place.)