Re: Add A Glossary - Mailing list pgsql-hackers

From Roger Harkavy
Subject Re: Add A Glossary
Date
Msg-id CAM-7Z-r5AZ_LxUi2Vs1_U-suM_iZRVgwBHow8Oh56QXu6Zk+0w@mail.gmail.com
Whole thread Raw
In response to Re: Add A Glossary  (Corey Huinker <corey.huinker@gmail.com>)
Responses Re: Add A Glossary
List pgsql-hackers
Hello, everyone, I'm Roger, the tech writer who worked with Corey on the glossary file. I just thought I'd announce that I am also on the list, and I'm looking forward to any questions or comments people may have. Thanks!

On Tue, Mar 10, 2020 at 11:37 AM Corey Huinker <corey.huinker@gmail.com> wrote:
This latest version is an attempt at merging the work of Jürgen Purtz into what I had posted earlier. There was relatively little overlap in the terms we had chosen to define.

Each glossary definition now has a reference id (good idea Jürgen), the form of which is "glossary-term". So we can link to the glossary from outside if we so choose.

I encourage everyone to read the definitions, and suggest fixes to any inaccuracies or awkward phrasings. Mostly, though, I'm seeking feedback on the structure itself, and hoping to get that committed.


On Tue, Feb 11, 2020 at 11:22 PM Corey Huinker <corey.huinker@gmail.com> wrote:
It seems like this could be a good idea, still the patch has been
waiting on his author for more than two weeks now, so I have marked it
as returned with feedback.

In light of feedback, I enlisted the help of an actual technical writer (Roger Harkavy, CCed) and we eventually found the time to take a second pass at this.

Attached is a revised patch.
 

pgsql-hackers by date:

Previous
From: "曾文旌(义从)"
Date:
Subject: Re: [Proposal] Global temporary tables
Next
From: Andreas Karlsson
Date:
Subject: Re: SERIAL datatype column skipping values.