Re: Elevator speech on DB2 development and web enablement?

[Henrik Rützou <hr@xxxxxxxxxxxx>]

Nathan

how du expect that triggers should signal back to the client (program) in a
common way that is supported in any program language SQL etc.?

On Sat, Oct 3, 2015 at 5:19 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

> Buck,
>
> You make a good point about a lack of tooling in regards to DB event
> procedures. It would be nice if developers could hover the mouse over any
> physical or logical file reference in any source member and be prompted to
> "open" any DB event source members pertaining to each file reference, for
> example.
>
> Such tooling would also ameliorate concerns about the "visibility" of code
> pertaining to cascading events.
>
> But I wouldn't delay the adoption of DB event handlers, waiting for tooling
> to make them more visible. After all, it would be nice if one could hover
> their mouse over any procedure reference in any source member and be
> prompted to open the source member where each procedure is defined.
>
> Soon after the adoption of DB event handlers, developers begin to view
> write, update, and delete statements the same way they view procedure
> calls. The benefits of implementing ILE concepts out-weighs the
> "visibility" that was available in the old days "monolithic" source
> members.
>
> Regarding the question of how broadly or narrowly to scope DB event
> handlers so as to avoid unintended consequences of cascading "calls", that
> question applies to standard procedures too.
>
> One might begin by writing DB event handlers for data validation purposes
> which are called before write and update operations. Once comfortable with
> the interface, branch out to business rules which are incidental to
> successfully completed updates (after triggers).
> --
> This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
> list
> To post a message email: WEB400@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/web400
> or email: WEB400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/web400.