B
bronco
Guest
But the help also mentions: Note: RETURN ERROR error-object-expression immediately returns to the caller before throwing the error object. Unlike a direct THROW, it ignores any CATCH blocks or ON ERROR directives in effect at the time of the RETURN. Although this doesn't mention FINALLY, if the CATCH is skipped you might as well assume that FINALLY is skipped as well. My suggestion would be to move away from RETURN ERROR altogether and use structured error handling, ie. undo, throw new AppError('sorry', -1). This plays nicely with catch and finally.
Continue reading...
Continue reading...