hard20 pts · first answer countspostgresqldata-modelling

Unique email with soft deletes

users has UNIQUE(email) and soft deletes via a deleted_at column. A user deletes their account and later signs up again with the same email, which fails with a unique violation. What is the best fix in PostgreSQL?

A.Replace it with UNIQUE(email, deleted_at)B.Drop the constraint and check for duplicates in application code before insertingC.CREATE UNIQUE INDEX ON users (email) WHERE deleted_at IS NULLD.Switch to hard deletes; soft deletes cannot work with unique columns

← Saving data and publishing an event Module variable holds the current user →