Tom Cole wrote:

>2. Alternatively, since we already return a vector of additional data, we could simply add the above items to the vector as ancillary data. This would presumably not change the "primary return code" for the entry points, but would allow someone post-processing the vector to get additional context to choose a proper SQLSTATE. If this route was chosen, I'd prefer to add an explicit additional state for underflow/overflow like isc_arith_overflow or something similar.
>
>
>
>

It's called a secondary code, not data. The idea is that the primary
code is fixed by architecture but secondary codes can change between
versions and implementations.

--

Jim Starkey, Senior Software Architect
MySQL AB, www.mysql.com
978 526-1376