public inbox for [email protected]
help / color / mirror / Atom feedFrom: Peter Eisentraut <[email protected]>
To: Ishaan Adarsh <[email protected]>
To: [email protected]
Subject: Re: [DOC] Introducing Quick Start Guide to PL/pgSQL and PL/Python Documentation
Date: Tue, 19 Dec 2023 16:48:14 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+oefZ72dLzRzgDe0VU01b7m4+A2bkQnZfXSuvXSzV7QHm0R3Q@mail.gmail.com>
References: <CA+oefZ72dLzRzgDe0VU01b7m4+A2bkQnZfXSuvXSzV7QHm0R3Q@mail.gmail.com>
On 16.12.23 11:49, Ishaan Adarsh wrote:
> 1. Added a new section titled "Quick Start Guide" to both PL/pgSQL and
> PL/Python documentation.
> 2. Included step-by-step instructions for users to get started with
> these procedural languages.
> 3. Provided explanations, code snippets, and examples to illustrate key
> concepts.
The way I read it, that's not really what your patch does. Your patch
explains how to write an extension in PL/pgSQL and PL/Python,
respectively. Which is okay, I guess, but a bit unusual. But I
wouldn't call that an unqualified "quick start" in the respective
languages. Also, it seems to repeat the very basics of setting up an
extension file structure etc. repeatedly in each chapter.
The existing documentation has "explanations, code snippets, and
examples". Are they not good? Do you have more? Better ones? Why are
yours separate from the existing ones?
I think it would be useful to take a step back here and define the
purpose of a bit clearer.
view thread (2+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: [DOC] Introducing Quick Start Guide to PL/pgSQL and PL/Python Documentation
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox