Soft-deleting Postgres rows without losing the...

Six lines of code that let you release a unique-constrained slug back into the namespace without dropping the constraint. I want soft-delete on my blog posts. I also want slug to be UNIQUE NOT NULL. These two requirements quietly fight each other, and the standard fixes — partial unique indexes, deleted_at IS NULL predicates, separate archive tables — are all heavier than what I needed. Here's the six-line trick I shipped instead. The conflict A blog post has a URL slug like my-cool-post. I want