Expanding Data Protection with Check Constraints and Triggers

  • Louis Davidson
  • Jessica Moss

Abstract

One of the weirdest things I see in database implementations is that people spend tremendous amounts of time designing the correct database storage (or, at least, what seems like tremendous amounts of time to them) and then just leave the data unprotected with tables being more or less treated like buckets that will accept anything, opting to let code outside of the database layer to do all of the data protection. Honestly, I do understand the allure, in that the more constraints you apply, the harder development is in the early stages of the project, and the programmers honestly do believe that they will catch everything. The problem is, there is rarely a way to be 100% sure that code written will always enforce every rule.

Keywords

Error Message Check Constraint Constraint Error Range Check Commit Transaction 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Copyright information

© Louis Davidson 2016

Authors and Affiliations

  • Louis Davidson
    • 1
  • Jessica Moss
    • 2
  1. 1.AntiochUSA
  2. 2.MechanicsvilleUSA

Personalised recommendations