Reading Error Messages
Fix mistakes fast.
Everyone writes broken queries. Beginners, experts, everyone. The difference is that experts read the error message, and fix it in seconds. Error messages look scary, but they're actually trying to help you. Let's break some queries on purpose, and learn to read what SQL tells us.

- Everyone writes broken queries
- Experts read the message
- Errors are trying to help
No such column
Here's a typo. Prise, with an S. Run it. No such column, prise. And look, SQLite even points an arrow at the exact word. The fix is to check the spelling against the table.
SELECT title, prise
FROM books
LIMIT 3;Parse error near line 1: no such column: prise
SELECT title, prise FROM books LIMIT 3;
^--- error hereNo such table
Same idea, but with the table name. Book, instead of books. Run it. No such table, book. Table names have to match exactly.
SELECT title
FROM book;Parse error near line 1: no such table: book
Fixed
Fix the spelling, and it works. Run it. When you see no such column, or no such table, it's almost always a typo, or the wrong table.
SELECT title, price
FROM books
LIMIT 3;โโโโโโโโโโโโโโโโโโโโโโฌโโโโโโโโ โ title โ price โ โโโโโโโโโโโโโโโโโโโโโโผโโโโโโโโค โ The Silent Orchard โ 14.99 โ โ Code of the River โ 12.99 โ โ Stars Over Lagos โ 9.99 โ โโโโโโโโโโโโโโโโโโโโโโดโโโโโโโโ
Summary
No such column, and no such table, mean a name doesn't match. Check the spelling. Next, syntax errors.
Key takeaways- no such column
- no such table
- Check the spelling