| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Post Gresql <postgresql(at)taljaren(dot)se> |
| Cc: | "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 42.6.8 trapping errors |
| Date: | 2020-11-15 06:25:43 |
| Message-ID: | CAKFQuwbCNhBoD4gDV8JE9rTGLsswmdkaaiMHPMVUjK5pZefPhQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Saturday, November 14, 2020, Post Gresql <postgresql(at)taljaren(dot)se> wrote:
> On 2020-11-15 04:39, David G. Johnston wrote:
>
> On Saturday, November 14, 2020, PG Doc comments form <
> noreply(at)postgresql(dot)org> wrote:
>
>> The following documentation comment has been logged on the website:
>>
>> Page: https://www.postgresql.org/docs/13/plpgsql-control-structures.html
>> Description:
>>
>> Hi
>> I think that section should have more examples with the most common
>> errors,
>> like for example no_data_found when doing a select.
>>
>
> Why?
>
> David J.
>
> I think it would be helpful from the perspective for an inexperienced user.
>
Doing “five whys” in email feels strange...
At least propose your idea of a comprehensive listing, i have no idea what
would be a common error - the feature itself is rarely used in the first
place. One plugs in whichever error is staring them in the face.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jürgen Purtz | 2020-11-15 18:45:35 | Re: Additional Chapter for Tutorial |
| Previous Message | Post Gresql | 2020-11-15 06:13:17 | Re: 42.6.8 trapping errors |