× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. WEB400
  3. October 2015

Re: Elevator speech on DB2 development and web enablement?

On 10/4/2015 5:13 AM, Henrik Rützou wrote:
To my best knowledge a trigger, even if it is executed before the I/O,
isn’t able to prevent the I/O being done so triggers are limited unless you
at the same time as you build in a validation and a way to message back to
the caller (that is not standard in a trigger) and combines it with
commit/rollback in the caller.

One can use a Before Trigger to prevent an I/O operation! To signal a
failure, have the trigger send an escape message to the caller, which
will be the database manager. The DB manager sees that and percolates
an I/O error back up to the HLL. In the case of an RPG program
performing an UPDATE, the UPDATE operation will receive the I/O error
and this is how the program knows the I/O did not happen.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.