Lesson: Never Use SQLite When Supabase Available

Mistake

Set up SQLite for watchlist storage in Hedge backend when we have a proper Supabase Postgres database.

Why It Happened

• Lazy "quick local storage" thinking
• Wanted to "just get it working" without proper setup

Fix Applied (2026-02-17)

1. Deleted hedge.db SQLite file
2. Rewrote db.py to use Supabase Python client
3. Updated watchlists router
4. Commit: 47e0bb0

Rule Going Forward

ALWAYS use Supabase for persistence. Never create local databases.

• Each project has its own Supabase (see PROJECTS.md)
• SQLite is never acceptable
• "Quick and dirty" leads to technical debt

Henry's Words

"What are you doing messing with SQLite? We have a full Postgres set up on Supabase!!!"