Re: Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: dustin sallings <dustin(at)spy(dot)net>
Cc: Stephan Doliov <statsol(at)statsol(dot)com>, pgsql-novice(at)postgreSQL(dot)org, pgsql-general(at)postgreSQL(dot)org
Subject: Re: Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
Date: 1999-02-12 14:21:27
Message-ID: Pine.BSF.4.05.9902121020450.13898-100000@thelab.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 11 Feb 1999, dustin sallings wrote:

> On Fri, 12 Feb 1999, The Hermit Hacker wrote:
>
> // Like, pgsql-docs(at)postgresql(dot)org :) How much of what is already
> // done by the Docs Team pertinent to all this, and, if not, why not?
> // If our existing manuals don't make good documentation, then why not,
> // and shouldn't those be fixed too?
>
> It's not that the docs are bad, it's just that they're not on a
> shelf. :)

My point was that why re-create the wheel...why not bundle *those* up and
improve upon what is already there?

> // > > //
> // > // > Since we are tossing ideas around, here is my two cents.
> // > // > .1c In order not to worry about royalties we can donate proceeds to
> // > // > PostgreSQL.
> // > // Amen/Bravo! This would truly be in the spirit of PostgreSQL
> // > //
> // > // Regarding the books contents. I think
> // > // I. Section 1 - Intro
> // > // 1. Brief Overview History
> // > // 2. Getting and Installing
> // > // 3. Setting up a Database
> // > // 4. Maintaining a Database
> // > // II. Section II - Making it work
> // > // 1. Postgres' type system
> // > // 2. Triggers & Functions
> // > // 3. Embedded Scripting Languages
> // > // a) pl/pgsql
> // > // etc.
> // > // 4. External access to postgres
> // > // a) libpq
> // > // b) libpq++
> // > // c) odbc
> // > // etc.
> // > // 5. Interfacing PostgreSQL to the Web
> // > // a) perl
> // > // b) php3
> // > // c) pygreSQL
> // > // others
> // > // III. Reference and Tekkie Stuff
> // > // 1. The built-in functions
> // > // 2. Query Optimization
> // > // 3. Postmaster tuning & performance issues
> // > // IV. New Features
> // > // This would be a section where people could insert information related to
> // > // the latest release. Much like law reports have addenda inserts at the
> // > // back.
> // > //
> // > // my $0.02
> // > //
> // > // steve doliov
> // > //
> // > //
> // > //
> // >
> // > --
> // > Principal Member Technical Staff, beyond.com The world is watching America,
> // > pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin(at)spy(dot)net>
> // > | Key fingerprint = 87 02 57 08 02 D0 DA D6 C8 0F 3E 65 51 98 D8 BE
> // > L______________________________________________ and America is watching TV. __
> // >
> // >
> //
> // Marc G. Fournier
> // Systems Administrator @ hub.org
> // primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
> //
> //
>
> --
> Principal Member Technical Staff, beyond.com The world is watching America,
> pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin(at)spy(dot)net>
> | Key fingerprint = 87 02 57 08 02 D0 DA D6 C8 0F 3E 65 51 98 D8 BE
> L______________________________________________ and America is watching TV. __
>

Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message The Hermit Hacker 1999-02-12 14:22:35 Re: Subject: Re: [GENERAL] A book for PgSQL? A need? yes? no?
Previous Message jose' soares 1999-02-12 14:06:50 Re: [GENERAL] A mistake generates strange result