Click any tag below to further narrow down your results
Links
Query the Murder is a free, no-login browser game that teaches SQL by having you query tables of suspects, alibis and events to solve Agatha Christie-inspired murder cases. It has 18 cases that build from basic SELECT and WHERE up to JOINs, GROUP BY, subqueries and window functions.
- The 18 cases are based on Agatha Christie novels such as Murder on the Orient Express and Endless Night, and each one uses a real database you query to check alibis and follow clues.
- Each case asks five SQL questions, and you name the killer by solving the last one.
- It targets beginners, analysts preparing for SQL interviews, and teachers who want a classroom activity without student logins.
SurrealDB 4 is a database engine that runs two ways: as serverless instances on Cloudflare (SurrealDB Earth) and as multi-node clusters over object storage (SurrealDS). The release is pitched on speed, durability, and compatibility with Postgres, MySQL, and MongoDB clients.
- Benchmarks claim indexed queries run 22x faster than 3.x, full-table scans 2.3x faster, and basic CRUD operations 42% faster, measured with crud-bench on the same hardware.
- Writes on SurrealDS are acknowledged only after being stored in two separate zones, and a new node recovers from the surviving copy.
- Existing PostgreSQL, MySQL, and MongoDB clients can query the same records as SurrealQL through one query planner.
This is a free, searchable directory of 575 open-source projects and companies built on DuckDB, the embedded analytics database. It's rebuilt from the awesome-duckdb GitHub list and updated as of October 2026.
- The map covers 516 open-source projects and 59 companies that publicly say they build on DuckDB, each linked to its source.
- The most-starred projects include PyGWalker (16K stars), Kepler.gl (12.1K), and Lance (7.2K), and the top UIs are Preswald and Online DuckDB Shell.
- Snowflake's own Snowset data shows 96.2% of queries scanned under 10 GB, a size one DuckDB instance can handle, so many workloads could move off a warehouse.
MotherDuck's Jev is a decision model that classifies text by picking from predefined answers, running 30x faster than GPT at 1% of frontier model costs. The article walks through five real use cases—grading AI agent logs, analyzing Hacker News sentiment, screening sales calls, and others—with actual SQL queries and datasets you can attach and rerun.
- Jev classifies 100,000 items in 82 seconds at ~1% the cost of frontier models by constraining outputs to a closed list you define, returning typed columns with confidence scores.
- On Hacker News mentions, 89% of pre-2023 "Claude" and "Anthropic" matches were false positives (Claude Shannon, the anthropic principle), but Jev's name-checking reduced false positives to 0.8% post-2023 when the products actually launched.
- The pattern separates facts from judgment: SQL extracts exact counts from logs or data, Jev only answers subjective questions like "was this turn efficient?" or "is this negative?", keeping costs down while maintaining accuracy.
DuckDB 2.0 Alpha adds dynamic attach statements that let you pull credentials from environment variables instead of hardcoding them, solving a major friction point when working across multiple data lakes. Early production testing shows less than 1% failure rates, and the release bundles this with Quack and official DuckLake support to make local-first lakehouse workflows actually practical.
- Dynamic attach statements now accept environment variables for credentials (usernames, passwords, account numbers), eliminating the need to hardcode sensitive data or switch to Python for multi-catalog federation
- Production pilot running hourly jobs showed <1% failure rate over 10 days, reading Parquet from S3 and writing to Iceberg tables via RDS-DMS
- Release combines dynamic attach with Quack and official DuckLake support, completing the local-first lakehouse story but raising open questions about concurrent writer behavior on shared Iceberg tables
The article examines why translating natural language into SQL for live data warehouses remains a tough problem. It traces the rise of ad-hoc queries in 1990s‐era historical data stores and shows how schema complexity and performance needs outpace current text-to-SQL systems.
- Benchmarks like Spider (max 200 tables, single database per task) don't reflect real enterprise warehouses with hundreds of tables and thousands of columns spanning dozens of schemas
- Production metadata is messy: cryptic/inconsistent column naming, typos, abbreviations, and mixed-language query logs undermine model performance
- Vendor-specific SQL extensions (Oracle's LISTAGG, PostgreSQL's JSONB operators) and user-defined types routinely break academic text-to-SQL models
- The authors call for shared benchmarks built from anonymized real industry schemas/workloads and argue LLMs need integration with metadata services and human feedback loops before replacing analysts in critical settings
OpenAI’s data productivity team built Kepler, an AI agent that understands their data platform context and writes iterative SQL to answer complex data questions. It handles table discovery, query refinement, follow-up prompts and even visualizations, cutting analysis time and reducing errors.
- OpenAI built Kepler, an internal AI agent that writes iterative SQL to answer data questions across 70,000 datasets and 600 petabytes daily, deployed via Slack, IDEs, or web UI
- It doesn't just query once—it discovers tables, refines CTEs, verifies numbers against dashboards/Notion, and proposes hypotheses (e.g., duplicate logging) for anomalies like a WAU spike
- Memory for self-learning plus rigorous evals let it improve over time without regressing
- Rolled out to 80% of the company, turning multi-engineer, multi-hour investigations into minutes
PgQue is a pure SQL/PLpgSQL event queue for Postgres 14+ that delivers durable, Kafka-style streams without dead tuples or external daemons. It uses snapshot-based batching and TRUNCATE-driven table rotation for stable performance under sustained load. A pg_cron (or any scheduler) ticker drives 1–2 second end-to-end delivery.
- Uses snapshot-based batching with TRUNCATE-driven table rotation instead of per-row UPDATE/DELETE with SKIP LOCKED, avoiding dead tuples, VACUUM pressure, and bloat under sustained load.
- Pure SQL/PLpgSQL install (single file) with pg_cron ticking every second, so it runs on managed Postgres without C extensions or custom builds—unlike PgQ, PGMQ, River, Que, and pg-boss.
- Offers Kafka-style shared event logs with independent per-consumer cursors, rather than one-job-one-worker task queue semantics.
- Delivery latency is 1–2 seconds (tick interval plus polling), with microsecond function execution—fine for durability-focused use but not for sub-millisecond dispatch needs.
Rill’s Metrics SQL lets you define business metrics once and query them using plain SQL across dashboards, notebooks, and AI agents. It compiles metric views into optimized OLAP queries, handling grouping, filters, time functions, and security automatically.
- Define a metric once in a YAML-backed metrics view and query it as plain SQL from dashboards, notebooks, and AI agents alike, instead of redefining it in dbt, Looker, Python, etc.
- A parser/compiler/executor pipeline rewrites simple queries like "SELECT country, revenue FROM revenue_metrics" into full OLAP SQL with correct GROUP BY, joins, and filters automatically.
- Security (row-level and column permissions) and SQL-injection-safe parameter binding are enforced consistently at the executor stage for every consumer.
- Works across multiple backends (ClickHouse, Snowflake, DuckDB, Druid) and can leverage existing database optimizations like materialized views and indexes for performance.
The author shares their shift from using Excel and Google Sheets to DuckDB and SQL for handling CSV files, highlighting the efficiency of querying data directly. They discuss the benefits of using SQL for data manipulation and invite readers to share their own CSV handling tips.
- DuckDB lets you run SQL directly on CSV files (joins, window functions, dedup queries) without importing them into Excel/Sheets first
- You can query CSVs from URLs or cloud storage like S3 directly, and export results straight back to CSV
- Several users find SQL queries more intuitive than replicating the same logic with spreadsheet formulas or pivot tables
- Some commenters mix in Parquet files and other extensions alongside DuckDB to further speed up ad-hoc analysis
Since the inception of SQL in 1974, there has been a recurring dream to replace data analytics developers with tools that simplify the querying process. Each decade has seen innovations that aim to democratize data access, yet the complex intellectual work of understanding business needs and making informed decisions remains essential. Advances like AI can enhance efficiency but do not eliminate the crucial human expertise required in data analytics.
- SQL was designed in 1974 by IBM's Chamberlin and Boyce specifically to let non-programmers query data in plain English, yet this self-service dream has resurfaced every decade (OLAP in the 80s, semantic layers now) without ever eliminating the need for developers.
- AI can now generate SQL and build analytical models faster than ever, but it automates only the mechanical coding, not the judgment calls about which metrics or definitions actually matter.
- The real bottleneck was never syntax or tooling but the intellectual work of understanding business context — a gap AI accelerates around but doesn't close.