惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

P
Proofpoint News Feed
博客园_首页
WordPress大学
WordPress大学
大猫的无限游戏
大猫的无限游戏
有赞技术团队
有赞技术团队
阮一峰的网络日志
阮一峰的网络日志
Hugging Face - Blog
Hugging Face - Blog
博客园 - 【当耐特】
酷 壳 – CoolShell
酷 壳 – CoolShell
Y
Y Combinator Blog
Vercel News
Vercel News
The GitHub Blog
The GitHub Blog
T
The Blog of Author Tim Ferriss
云风的 BLOG
云风的 BLOG
博客园 - 司徒正美
Engineering at Meta
Engineering at Meta
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
J
Java Code Geeks
Stack Overflow Blog
Stack Overflow Blog
N
Netflix TechBlog - Medium
Martin Fowler
Martin Fowler
宝玉的分享
宝玉的分享
G
Google Developers Blog
Last Week in AI
Last Week in AI

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
The NOT NULL trap that killed my Cloudflare Worker at 2:47am
강해수 · 2026-06-19 · via DEV Community

강해수

A single ALTER TABLE statement took down one of my Workers mid-deploy. No maintenance window, no graceful fallback — just a wall of 500s while live traffic hit a broken schema.

D1 is SQLite under the hood, and SQLite's ALTER TABLE is one of the most restricted in any relational database. You can add a column. That's essentially it. No dropping columns, no type changes, no renames — not without a full table rebuild. Cloudflare's docs mention this, but they don't quite convey how fast it bites you in production. The specific error that woke me up:

Error: D1_ERROR: Cannot add a NOT NULL column with no default value [ code: 1 ]

I'd tried to add campaign_id TEXT NOT NULL to a live table. SQLite refused immediately — existing rows would violate the constraint the moment the column appeared. The migration halted, the Worker's code expected the column to exist, and every request that touched that table failed. The fix is obvious in hindsight: always pair NOT NULL with a DEFAULT value on any new column, or accept nullable first and tighten the constraint later. What's less obvious is when the DEFAULT approach isn't good enough — specifically, when an empty string or zero is semantically wrong for your data model. That's where the expand-contract pattern comes in: create a new table with the schema you actually want, copy the data across, drop the old table, rename. It's four SQL statements and it's the only safe path for type changes or true column drops in D1.

I've now run this flow on 3 live D1 databases since early 2025. The discipline that actually saves you is boring: apply to local first (wrangler d1 migrations apply --local), verify with PRAGMA table_info(...) after every migration, and keep migrations in numbered flat files with no fancy tooling between you and the SQL. Five wrangler commands cover every scenario I've hit.

I wrote up the full breakdown — including the complete expand-contract SQL, the exact wrangler commands I run for each step, and how to verify column state before touching production — over on dailymanuallab.com.

Full post →