Re: Do we need "Diagnostics" sections of SQL command reference pages?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: josh(at)agliodbs(dot)com
Cc: pgsql-docs(at)postgresql(dot)org
Subject: Re: Do we need "Diagnostics" sections of SQL command reference pages?
Date: 2003-09-03 21:31:09
Message-ID: 14583.1062624669@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Josh Berkus <josh(at)agliodbs(dot)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

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Peter Eisentraut 2003-09-03 22:12:27 Re: Do we need "Diagnostics" sections of SQL command reference
Previous Message Bruce Momjian 2003-09-03 20:29:12 Re: [DOCS] German FAQ update