Data Foundations / sql-databases

SQL and databases

Relational querying, indexing, transactions, OLTP/OLAP modeling, and vector search basics.

shellbackend needed later
Focus
  • joins and window functions
  • indexes and explain plans
  • transactions
  • pgvector and ANN
Future feature idea

Query-plan visualizer for joins, windows, indexes, and vector search.

Self-check
  1. What is the core job of "SQL and databases"?
  2. Which common mistake would break a production implementation of this topic?
  3. Which inputs or limits must be validated before the interactive feature ships?
  4. What is the smallest test that proves the future implementation behaves correctly?
  5. When does this module really need backend compute, and when is a UI simulation enough?
Implementation notes
  • Start with one focused feature, not a full course inside one page.
  • All public inputs must be typed, bounded, and covered by reject-case tests.
  • If a model, dataset, or job is added, document source, license, limits, and fallback.
  • The interaction must explain the topic rather than serve as decoration.