|
Archives of the TeradataForumMessage Posted: Tue, 22 Nov 2005 @ 18:08:45 GMT
<-- Anonymously Posted: Monday, November 21, 2005 20:39 -->
The main difference is in the proximity that the business process has with the application interface (never mind the different skill sets required if one were to keep them separate). A high level 4GL can insulate a developer from the minutia of coding DML whereas a SP does not. That's a big difference. More important is that a 4GL piece of code that is close to the application interface will have a far easier time being unit and system tested. 4GLs come with error handling routines to test SQL Codes from multiple platforms and also have built in debugging and trace facilities to perform unit and system testing and debugging. SP's do not have any of those benefits and must be tested in a STAND ALONE mode. IMHO, the closer the business process it is to the procedure that implements it, the easier it is to document, build, share, and maintain. That means coding the business processes using the same high level languages that implement the interfaces. Anonym
| |||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | |||||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | |||||||||||||||||||||||||||||||||||||||||||||||||||