Josh Berkus <josh@agliodbs.com> writes:
> I agree that we don't need descriptions of the meaning of each error message
> in the command documentation.
> However, the listing of potential error messages is *very* useful to
> application coders for doing automated handling of errors. Since we are now
> supporting SQLSTATE responses, perhaps we could have error code ranges for
> the commands? Or is that totally unreasonable?
It seems completely impractical to guarantee that any particular command
can produce only some-small-subset of all the possible errors. There
are too many layers of code involved in handling any SQL command.
regards, tom lane