
text vs varchar in PostgreSQL and Supabase: the real difference, why varchar(255) is a MySQL habit, how to limit length and what a beginner should pick.
Optimistic locking in plain words: how two editors silently overwrite each other, and how a version column in your database catches the conflict before it lands.

A singleton, explained simply: one instance for the whole app. Why hot reload multiplies database connections and how globalThis fixes it.

SQL injection is when text from a form becomes a command for your database. We use an apostrophe in a surname to show why «stripping quotes» never works.

Your database dump won't restore: a pg_dump version error, the wrong file format, or ownership permissions. Three causes and the exact commands that fix them.

Database normalization in plain words: the three problems of a wide table, the three normal forms explained simply, and when duplicating data is actually right.

JOINs in plain words: how to stitch two tables in one query, how INNER differs from LEFT, and the two traps that make the total in your report wrong.

Foreign keys in plain words: how the database blocks orders from users who don't exist, what ON DELETE CASCADE does, and why you must add the index yourself.

How to add an audit log to your database: a PostgreSQL trigger in 20 minutes, recording the real app user, and locking the journal against edits. With code.

Backups and replicas protect against different things: a replica against a dead server, a backup against your own mistake. The difference, and what to pick.

A soft delete marks a row as deleted instead of removing it. Why apps do this, and the three traps every beginner walks into — including one that locks users out.

Step by step: how to dump your database with one command, where to keep the copy and how to prove it works. Plus the trap — files aren't in that backup.

A schema is the shape contract for your data: tables, fields, types. Here's how it catches garbage at write time — and where it hides in «schemaless» databases.

A deadlock is a mutual block: two processes hold a resource each and wait for each other forever. How the database detects deadlocks — and how not to create them.

How to add pagination to your app: the working path from simple OFFSET to a cursor. Five steps, real code, and why posts repeat across pages.

Database connection errors: too many clients, ENETUNREACH and failed authentication. Diagnose each one by its symptom and fix it.

Primary keys in plain words: what they're for, why email makes a bad key, and what to pick — auto-increment, UUIDv4 or UUIDv7.

A database transaction is all-or-nothing for a group of queries. Here's what it's for, how COMMIT and ROLLBACK work, and where beginners quietly lose data.

Spreadsheets don't break on volume: 10 million cells is fine. Here's where they actually break, where a database is overkill, and what to pick.

Why a database query is slow: the three real causes, how to check each in a minute, and how to fix it. Starting with the most common — a missing index.

A UUID is a long id like 550e8400-e29b-41d4… Here's why it beats 1, 2, 3, what plain numbers leak, and what the new UUIDv7 fixes.

Your app flew on 200 rows and died on 50,000. What a database index is, how to spot a missing one with a single command, and which columns deserve one.

SQLite is a database in a single file next to your code; Postgres is a separate server. An honest comparison: setup, deploys, users — and what to pick.

A database migration isn't moving data — it's a version of your table structure. What it is, how it works, and why you need one even solo.

How to add search to your app: 4 levels from an in-memory filter to search by meaning. Start with one line of SQL — most projects never outgrow it.

PostgreSQL and MySQL are both free SQL databases, but tuned for different things. We compare on cost, learning curve and use case — and say plainly what to pick.

An ORM is a translator between your code and your database: you write user.save() instead of an SQL query. Here's what it's for — and where its big catch hides.

SQL is strict tables with relations, NoSQL is flexible document-cards. We compare them where it counts and say plainly what a beginner should take.

You don't need to run a server: a free database goes live in 10 minutes. A step-by-step walkthrough on Supabase — from empty project to your first row.

A database is an app's memory that survives a restart. Explained simply: what it's for, how it's built, and when you actually need one.