pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chairudin Sentosa Harjo <chai@prima.net.id>
To: Bruce Stephens <bruce@cenderis.demon.co.uk>
Cc: PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Cc: PostgreSQL-documentation <docs@postgreSQL.org>
Subject: Re: [HACKERS] Re: [DOCS] Outline for PostgreSQL book
Date: Thu, 14 Oct 1999 08:24:28 +0700
Message-ID: <380530CC.165E6D48@prima.net.id> (raw)
References: <199910121716.NAA29586@candle.pha.pa.us>
	<87u2nw8c6x.fsf@cenderis.demon.co.uk>

Bruce Stephens wrote:
> 
> 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.)
> 
> ************


I second this opinion.



view thread (50+ messages)  latest in thread

Message-ID: <380530CC.165E6D48@prima.net.id>
Permalink:  ../380530CC.165E6D48@prima.net.id/
Also on:    postgresql.org/message-id/380530CC.165E6D48@prima.net.id

 · 

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: pgsql-docs@postgresql.org
  Cc: chai@prima.net.id, bruce@cenderis.demon.co.uk, pgsql-hackers@postgreSQL.org, docs@postgreSQL.org
  Subject: Re: [HACKERS] Re: [DOCS] Outline for PostgreSQL book
  In-Reply-To: <380530CC.165E6D48@prima.net.id>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox