Tag
32 articles tagged #Database.
P.01SQL injection is still landing CVSS 10.0 vulnerabilities in production software in 2026, including the Metabase bug that led to real breaches this month. Here's how parameterized queries actually stop it, where ORMs quietly reintroduce the bug, and how to verify your app is actually safe.
P.02An index turns a table scan into a handful of comparisons, but only for the queries it was built for. Here's how B-tree indexes work under the hood, when clustered and non-clustered indexes diverge, and why adding one can slow down writes you weren't thinking about.
P.03Four different philosophies for the same problem: getting a database schema from what it is to what it should be, safely, in a team. Here's how Flyway, Liquibase, Prisma Migrate, and Atlas actually differ, and which one fits your stack.
P.04Two requests try to update the same row at the same time. Pessimistic locking stops one of them from starting; optimistic locking lets both run and catches the conflict at the end. Here's how each works, with real SQL, and how to pick.
P.05Soft delete keeps a deleted_at column and hides rows instead of removing them. It sounds like the safe default, but it quietly breaks unique constraints, foreign keys, and query performance if you don't design for it up front. Here's the real tradeoff.
P.06Partitioning and sharding both split data up, and people mix up the terms constantly. Partitioning stays on one database and one server. Here's how range, list, and hash partitioning actually work, and when a partitioned table solves your problem before you need sharding at all.
P.07Read Committed, Repeatable Read, Serializable: most developers pick whatever their ORM defaults to and never ask why. Here's what each isolation level actually prevents, what it still allows, and how to pick one on purpose.
P.08A practical comparison of the four vector databases most teams actually shortlist for RAG and semantic search, with real pricing models, when each one wins, and the one question that should decide it for you.
P.09MySQL 9 shipped a native VECTOR column type and distance functions, no extension required. Here's how it actually compares to Postgres plus pgvector for real semantic search workloads, with working syntax for both.
P.10PostgreSQL 18 shipped in September 2025 and is now on its 18.4 point release. With PostgreSQL 19 still in beta, here's what 18's async I/O, UUIDv7, virtual generated columns, and OAuth support actually mean for a production upgrade decision today.
P.11Event sourcing stores every change to your data as an immutable event, then derives current state by replaying them, instead of overwriting a row each time something changes. Here's what that actually buys you, and the real operational cost it isn't worth paying in most systems.
P.12CAP theorem gets summarized as 'pick two of three' so often that the summary has replaced the theorem. Here's what it actually says, why the real constraint only bites during a network partition, and how to pick a consistency model for a system you're actually building.
P.13In under three months, one developer rebuilt Postgres from scratch in Rust using AI coding agents, and pgrust now matches Postgres 18.3's output across more than 46,000 regression queries. Here's what it actually is, and isn't, and why it matters.
P.14Adding read replicas is the standard fix for a database under read load, but it introduces a gap between when data is written and when it's readable everywhere. Here's what replication lag actually does to your application and how to design around it.
P.15An N+1 query bug turns one page load into hundreds of database round trips. Here's what causes it, how to spot it in Django, Rails, and Prisma, and the eager-loading fixes that make it go away for good.
P.16PostgreSQL 19 Beta 1 shipped with a REPACK command that finally makes VACUUM FULL and CLUSTER safe to run without a maintenance window, plus parallel autovacuum and smarter async I/O. Here's what changed and what to test now.
P.17Database engineer is distinct from data engineer. One designs schemas, tunes queries, and manages production Postgres. The other builds pipelines. Here's how to hire the one who keeps your app fast.
P.18ClickHouse is a columnar database designed for analytical workloads. It answers queries over billions of rows in seconds that would take minutes in Postgres. Here's what application developers need to know.
P.19SQLite runs in every phone and browser. Turso extends it to the server and edge with replication, branching, and a network protocol. Here's when it makes sense.
P.20Most slow queries come from a small set of fixable problems: missing indexes, N+1 patterns, and over-fetching. This is the practical diagnostic and fix guide.
P.21The queries that destroy production Postgres databases share a small set of root causes. Here is how to find them, understand what EXPLAIN ANALYZE is telling you, and fix them without guessing.
P.22Neon separates storage from compute to make Postgres behave like a serverless resource. The branching feature is what actually changes the development workflow — here's how it works and when it's worth the migration.
P.23Connection exhaustion is one of the most common production failures for apps that scale. Here's how pooling works, which tool fits which setup, and the configuration decisions that matter.
P.24Add similarity search to your existing Postgres database using pgvector. Real setup, indexing strategies, and when you actually need a dedicated vector database.
P.25Every SaaS team eventually faces the multi-tenancy decision. The wrong choice creates migration pain later. Here's how to think through database-per-tenant, schema-per-tenant, and row-level security based on what your product actually needs.
P.26Running totals, rankings, moving averages, lag and lead comparisons: window functions handle the analytics queries that would otherwise require application-side loops or multiple round-trips. Here's how they work.
P.27Drizzle ORM has become the go-to choice for TypeScript projects that want type safety without the overhead of a heavy ORM. Here's how it works, how to migrate from Prisma, and when to use it.
P.28ALTER TABLE locks your database. Your migration takes longer than expected. Users get errors. Here's how to handle schema changes that don't interrupt production traffic.
P.29Nearly 200 developers urged Oracle to rethink MySQL's future. We break down the open letter, the governance crisis, the rise of PostgreSQL and alternatives, and what developers should do next.
P.30How we built an AI-powered interface that lets non-technical users query any database using plain English, eliminating SQL expertise requirements and democratizing data access.
P.31The database landscape is consolidating around Postgres while SQLite finds new life at the edge. Meanwhile, vector databases have become essential infrastructure for AI applications.
P.32EditorPickMaster SQL from basics to advanced — SELECT, JOIN, GROUP BY, ORDER BY, indexes, date functions, and more using SQLite with Python.