| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: Simplify COMMENT and SECURITY LABEL documentation |
| Date: | 2021-06-02 15:05:10 |
| Message-ID: | d015a28c-0e0b-a8d0-c2cc-5a56f9703332@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 01.06.21 17:56, Alvaro Herrera wrote:
>> +1 for the concept, but I feel that "live in" is a bit too informal
>> for this context. I'm too caffeine-deprived to instantly come up
>> with le mot juste; but perhaps "exist within" would be an improvement?
>
> The glossary uses "reside in".
I like that.
> I suppose that we should either use the same term that the glossary
> uses, or alternatively fix the glossary to use whatever term we decide
> to use here.
>
> I do notice now that I used the term "belong to" elsewhere in the
> glossary. That could use some cleanup.
I think "belong to" is a stronger relationship, like a column belongs to
a table. Kind of like DEPENDENCY_INTERNAL vs. DEPENDENCY_NORMAL.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-06-02 15:08:47 | Re: Simplify COMMENT and SECURITY LABEL documentation |
| Previous Message | Peter Eisentraut | 2021-06-02 15:00:54 | Re: Note that ALTER TABLE cannot alter generated stored columns |