On 2017-10-31 17:02, Charlie-gm wrote:
On 10/31/2017 4: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
For large applications (500+ tables) I usually require it. Smaller
apps... eh... I think there would still be benefits but I'm usually
building them so fast that end users won't take the time to provide a
complete enough picture to drive all RI rules. Sure, I could still do
them on my "internal design only" tables, but like you said, there is
some overhead associated. So in the smaller cases it's pretty
situational as to whether or not I use it.
My attitude is, generally, the more you can put "into" the database,
that "belongs" in the database, the better flexibility,
maintainability, and stability you'll get.
I am using triggers in one of my apps (FabNet) to make sure keys have
cascading updates/deletes elsewhere as needed.
_______________________________________________
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/[email protected]
** 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.
