C
ChUIMonster
Guest
For a "stopper" I can imagine it is a feature - you can catch the STOP condition in the startup procedure and then re-initialize your session. In a case like that you would want any UNDO variables and temp-tables to be properly undone. For a "terminator" it seems like there would be no point and you could just throw it all away. Of course if everything is defined NO-UNDO and if you are not writing code with lots of nested sub-transactions there ought not to be much to undo anyway so the sheer size of what you are seeing seems a bit off kilter. If they feel so inclined someone with knowledge of the internals can probably correct my ramblings and explain why it needs to be done the way that it is being done.
Continue reading...
Continue reading...