Just have another table to retain the pkey, date and reason why of all the "Remove From View" entities.
Now you can do an where NOT IN clause against this table to filter properly.
How do you manage mergers and cascading data?
Our clientele are the oligarchs in the food-oil industry. They will sell each other physical plants which are our direct trading partners.
When you want to keep the history of what that "Ship to address" has done over the past 5-10+ years what do you do?
On Thu, Nov 2, 2017 at 1:18 AM, AndyHC andy@hawthorncottage.com wrote:
Totally agree - my default would be an 'instead of Delete' trigger that set a deleted flag (and logged it), and all regular user views to filter on that flag.
On 02-Nov-2017 3:31 AM, Ted Roche wrote:
DELETE is one of the easist ways to screw up a database that doesn't have proper RI declared. Clients all the time ask to "delete" Customer X because they no longer work with them, business closed, got bought, or something.
<snip>
[excessive quoting removed by server]