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 <[email protected]> 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] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CAJidMY+tVz4V-vJn24e5_sotk3JGoekaaEfVqezQJ6YJ2=t...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
