| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Matemática A3K <matematica(dot)a3k(at)gmail(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Improve "3.6. Inheritance" tutorial |
| Date: | 2026-10-08 17:59:30 |
| Message-ID: | CAKFQuwb1=WmDfWUGnFb9GrWi-s=6UwDSF7zbDcE-GX9jXg9kJA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Thu, Oct 8, 2026 at 9:06 AM Matemática A3K <matematica(dot)a3k(at)gmail(dot)com>
wrote:
> In this direction, if the "basic" tutorial is sourced from the "full"
> tutorial, a comment on the
> documentation should be put ("This is sourced as a basic tutorial, this
> section should give
> an overview of the feature and be self-contained.") and then, rewrite the
> following to glue it.
>
> The full tutorial should be:
> - Overview
> - Details
> - Caveats
>
> and the basic tutorial should be:
> - Source from Overview
> - Note: "If you find this feature useful for your case, continue reading
> here where you will find
> a more detailed discussion and the caveats to consider."
>
> Something like this is what came to your mind?
>
Seems like an all-or-nothing proposal that is quite different from what is
done today and doesn't contribute significant added value.
The interplay between the tutorial and the authoritative reference sections
are substantially correct today. I'd advise making any changes try and fit
within the current setup rather than trying to redesign the entire thing.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-10-08 18:09:55 | Re: Improve "3.6. Inheritance" tutorial |
| Previous Message | Tom Lane | 2026-10-08 16:41:07 | Re: Table 9.46. UUID Extraction Functions |