Dmitry Yemanov wrote:

>
> AFAIU, this could (should?) be achieved via a mapping table between
> GDSCODE's and SQLSTATE's (similarly to how SQLCODE's are handled) + one new
> API function (fb_sqlstate?). This way, GDSCODE's are still the primary error
> ids and nothing in the engine needs to be modified. The client passes the
> status vector to fb_sqlstate() and gets SQLSTATE value. PSQL code may be
> extended to support WHEN SQLSTATE <value> construct.
>
> Am I missing something?
>

No, sorry - you're right. That's a better solution.


Ann