Mike, >>Where's your preference in design with these in mind?<<
My philosophy is that the back end database, whatever it is, should be a dumb as a rock. A database should only be concerned with its internal integrity and no more. Anything else is pretty much geared toward vendor lock-in. But having noted that, FK constraints are absolutely a part of the data integrity. So yes, use 'em. Views? Sure, that's basically the only way to communicate. Business rules? Nope, stay away. That's for middleware. Bill Anderson On Tue, Oct 31, 2017 at 1:26 PM, < [email protected]> 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] _______________________________________________ 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/ca+o1engzhtfj1gwbcgotw+2boj9p17mtz8squse5dm+irr2...@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.
