Re: RPGLE STORED PROCEDURES

[jkrueger@xxxxxxxxxxxxx]

>> How are stored procedures different than triggers?  Or are they the same?
Conceptually speaking.

A trigger is a piece of code that is executed every time a particular event
happens.  For example, if you had a whole set of logic that you wanted to run
whenever a customer's address was changed, such as checking to see if the
customer needs to be reassigned to a different branch, you could register it as
a trigger against the customer address field, and have it called whenever the
field is changed.  Then it wouldn't matter how many applications there are that
potentially change the address, the database would take care of making sure your
program gets called for all changes.

A stored procedure is a program that you call from SQL;  typically, it does a
sequence of database related tasks, but can be called as a single database
operation.  For example, you could use stored procedures to 'read' and 'write'
an order, where the order was actually records spread across several different
files.  One of the reasons stored procedures are especially useful on the
AS/400, when writing distributed applications, is that the stored procedure can
adopt authority, and the remote users don't have to have direct access to the
database.

Janet Krueger
Andrews Consulting Group


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---