In order to prevent such mistakes in the first place, it’s important to understand what it means to delete a record and to establish good business-rules as a foundation to your system.
Unfortunately, some of the biggest database administrative headaches we’ve seen are a result of careless DELETE actions, and the removal of important data from a system. We've seen a lot of cases where developers put most thought into how records are added and retained, how data is modeled, and how data will link in a dynamic way - but not much thought is put into the removal of data from the system, and the consequences that might follow. All of our users are savvy, and all of their actions are intentional. When we envision data management solutions, we tend to think of perfect-use scenarios, where no one ever creates a duplicate record, no one accidentally hits the New Record button, no project is ever canceled, and certainly no errant script accidentally miscopies data. JEdited on SeptemUnderstanding the larger issues surrounding the Delete Button
0 kommentar(er)
