soft-delete-restore

Implement soft delete by adding a nullable deletedAt timestamp column to your data model. This marks records as deleted without permanent removal, enabling a consistent, auditable deletion lifecycle with data recoverability.

Add a recycle bin by utilizing a deletedAt timestamp pattern to mark records as deleted. This supports restore and optional hard-delete purge operations, providing safe data lifecycle control and cross-device restoration capabilities.

Cascading soft delete propagates the deletedAt timestamp marking across related data models. The service layer manages these cascading behaviors during softDelete and restore operations, ensuring referential integrity while preserving audit trails.

You need a soft delete pattern when your app requires audit trails, data recoverability, or safe data lifecycle control. It preserves records using a deletedAt field, supporting cross-device restoration and optional hardDelete purge paths.

Yes, a soft delete implementation can include an optional hard-delete purge path. This allows you to mark records as deleted with a deletedAt timestamp first, then permanently remove them from the database later if needed.

Yes, implementing a deletedAt pattern provides a consistent, auditable deletion lifecycle. By marking records with a nullable timestamp instead of erasing them, you maintain an audit trail and support safe data lifecycle control across your models.