To: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: PostgreSQL-documentation <docs@postgresql.org>
Subject: Re: [DOCS] Outline for PostgreSQL book
References: <199910121716.NAA29586@candle.pha.pa.us>
From: Bruce Stephens <bruce@cenderis.demon.co.uk>
Date: 12 Oct 1999 23:08:05 +0100
In-Reply-To: Bruce Momjian's message of "Tue,
 12 Oct 1999 13:16:35 -0400 (EDT)"
Message-ID: <87u2nw8c6x.fsf@cenderis.demon.co.uk>
User-Agent: Gnus/5.070096 (Pterodactyl Gnus v0.96) XEmacs/21.2 (Shinjuku)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Lines: 50

Bruce Momjian <maillist@candle.pha.pa.us> writes:

>                           PostgreSQL Book Proposal
>                                       
>                                Bruce Momjian

[...]

>    4.
>           Advanced SQL Commands

[...]


>    6.
>           Interfacing to the POSTGRESQL Database
>         (a)
>                C Language API
>         (b)
>                Embedded C
>         (c)
>                C++
>         (d)
>                JAVA
>         (e)
>                ODBC
>         (f)
>                PERL
>         (g)
>                TCL/TK
>         (h)
>                PYTHON
>         (i)
>                Web access (PHP)
>         (j)
>                Server-side programming (PLPGSQL and SPI)

Isn't (j) logically part of chapter 4?  (Or 5, if it's PostgreSQL
specific.)  Or am I completely confused?  (Where can I read about
PLPGSQL and/or SPI, other than in the forthcoming book?)

If it came to a choice between having very short sections in chapter
6, and having two or three of them covered in more depth, I'd go for
the latter.  

(Of course, you'll inevitably choose two or three which don't match
what many readers will want (whichever two or three you choose), but
even so, I think I'd get more out of a reasonably thorough coverage of
a couple of languages that I won't use than superficial coverage of
all of them which doesn't really reveal anything useful.)