dotnet falcon

OK, so we've got to the point where we have a good solution for flagging deleted entities. But we still have to find a way to filter out the flagged records from query results. Just as a reminder: we need a solution that works for entities, for related

Microsoft SQL Server has a little-known and little-used feature called cascade update. Just like cascade delete, which deletes the referring records along a FK, the cascade update feature updates the values of the FK in the referring entities if the referred value changes. So let's say you have

In the last post of the series, I identified a good enough solution to handle the EF soft delete scenario with good performance and no abstraction leaking. The solution itself contains a well-defined process, but ideally this process should be automatized as much as possible. Just a reminder about the

In Part 1 of this series I discussed what logical delete is, in Part 2 I gave a solution that is kinda good for cases when you don't have cascading requirements. But in that post I pointed out the solutions inadequacy to handle the cascading situation. Here in

So in my previous post in the series, I described what soft delete is and what challenges need to be overcome when implementing it using Entity Framework (since EF has no explicit support for this). Now, in part two, I want to discuss a naive solution — one that might satisfy