Tom,

The primary GDS code isc_arith_except should remain intact. But we should
add secondary GDS codes to separate between exception types, to carry some
context info, etc. For example:

{ isc_arg_gds, isc_arith_except,
isc_arg_gds, isc_string_trunc,
isc_arg_end }

So the SQLSTATE code could parse the entire status vector to find all GDS
codes that are necessary to make a decision about some definite SQLSTATE.
Yeah, it means that a simple GDSCODE->SQLSTATE mapping won't work, but it
was just a simplest solution, not the only possible one.


Dmitry