|
I have some of the same questions, so I will be interested in the responses. Regarding the first question, my only input is that if it is an existing database with programs already using it, forget constraints. It's almost impossible to reengineer a system. If it is a new database and you have control over the program design, they are wonderful tools, but almost require matching triggers to prescreen for the same errors that the constraint will encounter. This is so you can offer a "soft" failure of some sort, rather than the hard crash that results from a constraint violation. On #2, It depends. :-) On #3, I'm not sure what you mean by "data transport". I have been successful at moving my I/O into service program routines, but being generic, they contain no business logic. It probably would not be too hard to have the I/O modules themselves call specific business logic routines, based on the file data being requested, but I haven't tried to implement that yet. Again, this would probably only be practical on new designs. My biggest interest is how people are separating their presentations from the business logic. Are the business rules kept in some sort of maintainable table? And how are screen entry fields validated against the table in a manner that could be generic? > -----Original Message----- > From: MWalter@hanoverwire.com [SMTP:MWalter@hanoverwire.com] > Sent: Wednesday, April 10, 2002 11:07 AM > To: rpg400-l@midrange.com > Subject: Separation of Presentation, BL, and I/O Tiers > > Hello all, > > I am trying to define what would be required to separate our presentation > from business logic, from database I/O and would like your opinion on some > issues. Any input would be greatly appreciated. > > 1) How do you feel about physical file constraints to provide some field > validation? > 2) Does field validation belong in the database tier or the business logic > tier? > 3) What is the most advantageous method of data transport (Data > Structures, > Data Queue, Trigger)? > > I realize that these questions are quite broad and probably the most > obvious answer is 'It depends'. But what I'm looking for is options based > on personal experiences > > Thank you very much. > > Mark > > > Mark Walter > Sr. Programmer/Analyst > Hanover Wire Cloth a div of CCX, Inc. > mwalter@hanoverwire.com > http://www.hanoverwire.com > 717.637.3795 Ext.3040 > > _______________________________________________ > This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list > To post a message email: RPG400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l > or email: RPG400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/rpg400-l. ************************************************************************************************************************************************************************************************************ This message originates from Lincare Holdings Inc. It contains information which maybe confidential or privileged and is intended only for the individual or entity named above. It is prohibited for anyone else to disclose, copy, distribute or use the contents of this message. All personal messages express views solely of the sender, which are not to be attributed to Lincare Holdings Inc., and may not be copied or distributed without this disclaimer. If you received this message in error, please notify us immediately at MailAdmin@lincare.com or (800) 284-2006. ************************************************************************************************************************************************************************************************************
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.