MB Software Solutions General Account wrote: > Paul McNett wrote: >> I don't tend to put anything, even referential integrity constraints, in > the >> database. I like simple databases and smart rules at the biz layer. > Perhaps a cronjob >> on the server to monitor database integrity to delete orphans and email > me the >> actions taken, etc. > > > Ditto. I treat the databases a just storage, and put all of the > RI/rules/etc. into the Business Object layer. That affords me the > greatest flexibility in my designs, imo. And with my latest n-tier > framework, I can easily work my solutions with ANY database backend. The > key is to maintain that "disconnected is ok" kind of mentality in your > designs, instead of always relying on the "constantly connected" approach > of legacy Foxpro apps.
Yes and business rules need to be usable by potentially more than one app. For me that makes it essential that business rules are written in a language runnable cross-platform and with or without a GUI. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://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.
