M
Mike Fechner
Guest
BLOCK-LEVEL and ROUTINE-LEVEL Error handling is not relevant here, because the DO block does explicitly define an error handling option. At first sight I would have said it’s because the NO-UNDO option on the new temp-table: That would explain why the second record is not rolled back (deleted) before it’s catched. But even without the NO-UNDO option on the temp-table the code behaves the same. If you add the TRANSACTION keyword to the DO block (and don’t have NO-UNDO on the temp-table), then the second record will be rolled back before the CATCH (it’s no longer available in the CATCH). And you won’t see the errors. Von: piamaria [mailto:bounce-piamaria@community.progress.com] Gesendet: Donnerstag, 11. Juni 2015 11:23 An: TU.OE.General@community.progress.com Betreff: RE: [Technical Users - OE General] Catch not working as expected RE: Catch not working as expected Reply by piamaria Same result if I use BLOCK-LEVEL instead of Routine-LEVEL. Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...