Ambiguous error message when check constraint matches table name

We currently have 2 types of check constraints.

Field check constraints and table check constraints. If a column with a check constraint has the same name as a table check constraint for the same table, it is impossible to tell which check constraint failed.

create table test.t(a int, b int check(b>0),

                    constraint b check(a<b));

For either of the checks in the above table, the error message is:

CONSTRAINT b failed for test.t