The current language for defining triggers and stored
procedures is somewhat impoverished in the area of
loop control. The only way to break out of a loop is
with an exit, which breaks out of the current loop, any
outer loops, and the procedure. This leads to wrapping
procedures in other procedures for flow control. I'm
generally in favor of small, modular procedures, but
this seems like an awkward way to force people to simplify
their code.

The underlying BLR has a label and leave structure that
allows the code to break out of specific loop levels.
What should we use for language? One suggestion is to
emulate the label/leave model. Another is to use the
C/Delphi style 'break'.

Thoughts?

Regards,

Ann
www.ibphoenix.com
We have answers.