RDB$ERROR syntax extension

[pastorkaluga]

In addition to the MESSAGE, add a new context, p.e. CUSTOM_MESSAGE, to receive only a custom exception message, without exception number, name, and stack.

example MESSAGE

exception 113
ARN$ERROR
Invalid state change for used ticket
At procedure ARN$SET_STATE line: 176, col: 31
At procedure SALE$DOC_DELETE line: 131, col: 40
At procedure EXT$BILL_REFUND_START line: 111, col: 11
At procedure EXT$BILL_REFUND line: 49, col: 12.

example CUSTOM_MESSAGE

Invalid state change for used ticket

[mrotteveel]

I don't think CUSTOM_MESSAGE is the right term for that. Ideally, that would have been MESSAGE, and the current output would have been STACKTRACE or something like that. However, to retain backwards compatibility, I'd suggest that if we want to add something like that, it would need to be something like MESSAGE_TEXT.

That said, given how error messages (or rather, status vectors) are constructed, I'm not entirely sure such a clean separation is even possible (I'm not familiar with the internals of this).

[pastorkaluga]

MESSAGE_TEXT

good,
it can even be a TEXT