Soft delete keeps rows and sets deleted_at. Users can "undo" or audit history. It complicates unique constraints and queries unless you plan ahead.

The email-uniqueness trap

If users.email is unique, you cannot register the same email again after soft-delete unless you allow multiple rows or change strategy.

Partial unique index (PostgreSQL)

CREATE UNIQUE INDEX users_email_active
ON users (email)
WHERE deleted_at IS NULL;

Allows re-registration after delete while preventing duplicate active emails.

Query discipline

Default scopes should filter deleted_at IS NULL. Admin and restore flows must bypass explicitly.

Foreign keys

Decide whether child rows are soft-deleted with parents or left orphaned for analytics. Document cascade behavior in your ORM.

When hard delete wins

GDPR erasure, PII minimization, or tables that are purely operational may require true DELETE (or crypto-shredding).