Commented by: Alice F. Bird (firebirds)

Date: 2003-08-28 16:18
Sender: dimitr
Logged In: YES
user_id=61270

1. Explained by Ivan, i.e. you should use e.g. "GDSCODE
arith_except" instead of the numeric code
2. Reserved for future use. E.g. trigger messages are a
subject of convertion to system exceptions in v2.0
3. Partially fixed in v1.5

Commented by: Alice F. Bird (firebirds)

Date: 2002-08-27 04:10
Sender: helebor
Logged In: YES
user_id=60469

Adding a request to increase the maximum size of an exception string to something capable of realistically
returning a comprehensible message to the client.

Commented by: Alice F. Bird (firebirds)

Date: 2002-04-30 17:40
Sender: helebor
Logged In: YES
user_id=60469

Ivan, you cannot imagine how I struggled with gdscode possibilities!
You have just saved 60,000 lives.

Just a further question: is it possible to get at the following?
#⁠define isc_exception_datatype_missalignment 335544769L
#⁠define isc_exception_array_bounds_exceeded 335544770L
#⁠define isc_exception_float_denormal_operand 335544771L
#⁠define isc_exception_float_divide_by_zero 335544772L
#⁠define isc_exception_float_inexact_result 335544773L
#⁠define isc_exception_float_invalid_operand 335544774L
#⁠define isc_exception_float_overflow 335544775L
#⁠define isc_exception_float_stack_check 335544776L
#⁠define isc_exception_float_underflow 335544777L
#⁠define isc_exception_integer_divide_by_zero 335544778L
#⁠define isc_exception_integer_overflow 335544779L
#⁠define isc_exception_unknown 335544780L
#⁠define isc_exception_stack_overflow 335544781L
#⁠define isc_exception_sigsegv 335544782L
#⁠define isc_exception_sigill 335544783L

i.e.
WHEN GDSCODE exception_integer_divide_by_zero do...

Shouldn't it be consistent with the others?

Helen

Commented by: Alice F. Bird (firebirds)

Date: 2002-04-30 15:56
Sender: prenosil
Logged In: YES
user_id=89535

> 1. According to docs, exceptions can be trapped by using
> the GDSCODE keyword with WHEN, e.g.
> WHEN GDSCODE 35544778 do

This one is error in docs. GDSCODE should not be followed
by error number, but by its name.
E.g. to trap isc_arith_except use
WHEN GDSCODE arith_except DO

Another undocumented feature (?) is the fact that FB accepts
incomplete exception names. E.g. there are errors
isc_bad_dbkey, isc_bad_db_format, isc_bad_db_handle, etc.,
and any of these (probably, I did not test it much
thoroughly) can be trapped by:
WHEN GDSCODE bad_ DO
(At least FB accepts such command.)

> 2. According to the docs, "RDB$EXCEPTIONS ...
Do not you have RDB$TRIGGER_MESSAGES in mind ?

> 3. There seems to be no way to read either SQLCODE or
> GDSCODE into a host variable in a SP.
> when ANY do
> _SQLCODE = SQLCODE;

This would be very useful, and should be qualified as
feature request.