Re: Add A Glossary
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Corey Huinker <corey.huinker@gmail.com>, pgsql-hackers@postgresql.org
Date: 2019-11-25T07:55:07Z
Lists: pgsql-hackers, pgsql-docs
On Sat, Nov 09, 2019 at 09:19:16AM +0100, Fabien COELHO wrote: > On principle, I'm fine with having a glossary, i.e. word definitions, which > are expected to be rather stable in the long run. > > I'm wondering whether the effort would not be made redundant by other > on-line effort such as wikipedia, wiktionary, stackoverflow, standards, > whatever. > > When explaining something, the teacher I am usually provides some level of > example. This may or may not be appropriate there. That's exactly a good reason for being a reviewer here. You have quite some insight here. > I'd consider making SQL keywords uppercase. > > Developing that is a significant undertaking. Do we have the available > energy? 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. -- Michael
Commits
-
Glossary: Add term "base backup"
- 606c3845988d 14.0 landed
-
Minor glossary tweaks
- a0b2d583db9f 14.0 landed
- ac25e7b039d5 13.0 landed
-
Adjust some glossary terms
- 91a890bd7fef 13.0 landed
- 816cbb59e300 14.0 landed
-
Fix more typos and grammar problems in the glossary
- eeba6c7e4366 13.0 landed
-
Review of the glossary
- 756abe2bc760 13.0 landed
-
Add a glossary to the documentation
- 347d2b07fcc2 13.0 landed