Subject Re: Proposal to add SQLState to Vulcan
Author Bill Oliver
> I have used your data to add SQLstate mapping to Jaybird.
Following
> fixes (not yet complete, only what I have found):
>
> 335544510 - you have HY000 ("general"), should be 40001 ("lock
conflict").
>
> 335544439 - you have 23000 ("constraint"), should be either HY000
or 37000
>
> 335544595 - looks like it should be HY000, not 27000.
>

Thanks for those corrections, great!

I will make these changes:

UPDATE SYSTEM_ERRORS SET SQL_CLASS = '40', SQL_SUBCLASS = '001'
WHERE GDS_SYMBOL = 'lock_timeout';
UPDATE SYSTEM_ERRORS SET SQL_CLASS = 'HY', SQL_SUBCLASS = '000'
WHERE GDS_SYMBOL = 'dsql_trigger_err';

I think you must be off a bit for 335544439. I have this as
{335544439, "function %s could not be matched"}, /* 119, funmismat */

which I've mapped to 39000, External routine invocation exception.

FYI, I hope to push this to SF later this week - I have not yet
finished the push here locally. Our driver writer provided me a
playpen yesterday that I can use to test this with our stuff, so I
should be able to wrap this up shortly. We'll see.

-bill

p.s. Thanks, Jim for the earlier comment on the message file. In the
end, this did not require a change to the message file format, so I
did not need a new protocol number.