ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to architect multi‑tenant isolation and soft‑delete logic with EF Core’s Global Query Filters. This guide covers requirements, minimal design, data boundaries, operational checks, failure modes, and when to adjust the pattern.
Decide between EF Core Global Query Filters and manual Where clauses for soft deletes. Learn how to implement automated filtering using interfaces and how to avoid common migration pitfalls.
Stop manually adding .Where(x => !x.IsDeleted) to every query. Learn how to use EF Core Global Query Filters to implement a robust, systemic soft-delete pattern.
An architecture note on Azure Key Vault soft-delete and purge protection as the smallest recoverable control-plane design, covering trust boundaries, CLI verification, and failure modes.
EF Core Global Query Filters let you centralise soft‑delete logic. The filter automatically adds a WHERE clause to every query for a type, eliminating boilerplate and ensuring consistency. Learn how to configure, test, and be aware of common pitfalls.
Set up Sequelize paranoid soft delete so destroy marks deletedAt, normal queries hide rows, and restore or force delete remain available. Includes model setup, verification steps and recovery options.
Decide whether to use EF Core Global Query Filters for automatic soft‑delete handling, compare effort and trade‑offs, and see a concrete implementation and verification steps.
Paranoid soft deletes hide rows in Sequelize but leave them in the database, causing unique constraints like email to block re-registration. Learn how to verify filtering, restore, and design indexes around soft deletes.
EF Core global query filters automatically apply a WHERE clause to every query for an entity, enabling soft deletes and tenant isolation without repeating filters. This post covers configuration, a worked example, and the trade-offs you need to test.
entityframeworkcore
sequelize