Constraints stop some devs cold when they are trying to "clean up" their data.
It is in the correct space in the database because it protects the data there. Compliance auditors like it as well.
On Tue, Oct 31, 2017 at 3:26 PM, < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
At the day gig, they use FK constraints and References in their Oracle database schema. Honestly, I got into that years ago with VFP but then kinda fell off that wagon over the years, preferring to just handle some things in the BizObj of the solution rather than put more rules in the backend database. The idea was that if I changed backend databases, I wouldn't need to rewrite a whole bunch of specific DBMS code.
Where's your preference in design with these in mind?
[excessive quoting removed by server]