From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, jian he <jian(dot)universality(at)gmail(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: create table explicitly mention that unique|primary key constraint will create an |
Date: | 2024-01-18 21:21:55 |
Message-ID: | CAKFQuwZDggN=qaKt3N5rTaiRuzsWhgvF53cCBe+Bm4vFiyt5fQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Thu, Jan 18, 2024 at 7:54 AM Peter Eisentraut <peter(at)eisentraut(dot)org>
wrote:
>
> I find the specific change
> proposal for ddl.sgml a bit weird, though, because this is a very
> introductory section, and you are referring people to pg_class (what is
> that?!?) for details. If we want to put something there, it should
> respect the order in which that chapter introduces concepts.
>
>
I started looking at this specific item and immediately got the idea to
actually document in user-facing (i.e., not system catalogs) what these
object categories are in which object types share the schema namespace.
The "Other Object Types" section already in the DDL chapter seems to
provide a near-perfect place to put this (not sure I like the word "other"
there being my only complaint). The attached patch replaces Laurenz's v1,
leaving the create_table changes as-is but presenting an alternative
approach to introducing namespacing when we explain why schemas exist.
David J.
Attachment | Content-Type | Size |
---|---|---|
0001-Doc-objects-in-pg_class-share-a-namespace-v2.patch | text/x-patch | 6.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2024-01-19 10:46:46 | Re: create table explicitly mention that unique|primary key constraint will create an |
Previous Message | Peter Eisentraut | 2024-01-18 14:54:26 | Re: create table explicitly mention that unique|primary key constraint will create an |