Jonathan Neve wrote:

> Hi all,
>
> A while ago, I mentionned the issue of error messages, and suggested
> making them a bit clearer and more helpful, in particular, by
> providing (in as many cases as applicable), the table/column name,
> the value of column/parameter, the line number (in
> triggers/procedures), as well as just more precision for certain
> highly ambiguous error messages such as "Column unknown", "Arithmetic
> overflow or string truncation", or "Unknown datatype", etc.

What server version are you taking as an example?

Most of the cases of "Token unknown" and "Column unknown" were fixed in Fb1,
providing line and column information, that's almost totally accurate.

"Arithmetic overflow or string truncation" has been explained that's not
trivial to fix. When you get to it, there's no notion of tables and fields
but only descriptors (a structure that describes a value's attributes) two
levels below where field names can be determined.

"Unknown datatype" happens probably with parameters. What do you want to do
with it? Named parameters are mostly a client side facility. Most RDBMS
products use only "?" to signal a parameter.

C.