Re: the case for machine-readable error fields

>
> What are people doing with parsing error messages for "column names for
> datatype mismatches"?  I can't imagine any of my code being able to do
> anything sensible in such a case.  If it's things like people giving
> dates to the database in an incorrect format then that's what they get
> for not doing input validation isn't it?
>

When you have a full set of constraint, then you don't need to
validate input. Just you will execute statement. When execution is
correct, then all is ok, when not, then you have to recheck message,
err code, ... and you have to verify, so some exception is expected or
not. This is programming based on exceptions. Some better structured
information helps. And what's more - this should be in conformity with
ANSI SQL.

regards
Pavel Stehule