From: Chairudin Sentosa Harjo <chai@prima.net.id>
To: Bruce Momjian <maillist@candle.pha.pa.us>
Cc: PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Cc: PostgreSQL-documentation <docs@postgreSQL.org>
Subject: Re: [HACKERS] Outline for PostgreSQL book
Date: Wed, 13 Oct 1999 11:22:01 +0700
Message-ID: <380408E9.9D4F554A@prima.net.id> (raw)
References: <199910121716.NAA29586@candle.pha.pa.us>
You should put one special section to talk about DATE. (datetime,
abstime, etc..)
That is the most asked by the mailing list.
You could put tons of samples on how to use and manipulate DATE.
ie. How to get the time, how to get the minute, how to get the hour,
how to get the month in number (1,2,3,4),
how to get the month in word (JAN, FEB, MAR)
The most important thing is to have alot of samples.
Practical samples are more useful than just syntax.
Regards,
Chairudin Sentosa
> Bruce Momjian wrote:
>
> Here is my proposal for an outline for a PostgreSQL book. Many of us
> have been asked by publishers about writing a book. Here is what I
> think would be a good outline for the book.
>
> I am interested in whether this is a good outline for a PostgreSQL
> book,
> how our existing documentation matches this outline, where our
> existing
> documentation can be managed into a published book, etc.
>
> Any comments would be welcome.
>
> --
> Bruce Momjian | http://www.op.net/~candle
> maillist@candle.pha.pa.us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania
> 19026
> ...................................................................
>
> The attached document is in both web page and text formats.
> View the one which looks best.
>
> ---------------------------------------------------------------
>
> PostgreSQL Book Proposal
>
> Bruce Momjian
>
> 1. Introduction
> 2. Installation
>
> (a) Getting POSTGRESQL
> (b) Compiling
> (c) Initialization
> (d) Starting the server
> (e) Creating a database
> (f) Issuing database commands
> 3. Introduction to SQL
>
> (a) Why a database?
> (b) Creating tables
> (c) Adding data with INSERT
> (d) Viewing data with SELECT
> (e) Removing data with DELETE
> (f) Modifying data with UPDATE
> (g) Restriction with WHERE
> (h) Sorting data with ORDER BY
> (i) Usage of NULL values
> 4. Advanced SQL Commands
>
> (a) Inserting data from a SELECT
> (b) Aggregates: COUNT, SUM, etc.
> (c) GROUP BY with aggregates
> (d) HAVING with aggregates
> (e) Joining tables
> (f) Using table aliases
> (g) UNION clause
> (h) Subqueries
> (i) Transactions
> (j) Cursors
> (k) Indexing
> (l) Table defaults
> (m) Primary/Foreign keys
> (n) AND/OR usage
> (o) LIKE clause usage
> (p) Temporary tables
> (q) Importing data
> 5. POSTGRESQL'S Unique Features
>
> (a) Object ID'S (OID)
> (b) Multi-version Concurrency Control (MVCC)
> (c) Locking and Deadlocks
> (d) Vacuum
> (e) Views
> (f) Rules
> (g) Sequences
> (h) Triggers
> (i) Large Objects(BLOBS)
> (j) Adding User-defined Functions
> (k) Adding User-defined Operators
> (l) Adding User-defined Types
> (m) Exotic Preinstalled Types
> (n) Arrays
> (o) Inheritance
> 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)
> 7. POSTGRESQL Adminstration
>
> (a) Creating users and databases
> (b) Backup and restore
> (c) Performance tuning
> (d) Troubleshooting
> (e) Customization options
> (f) Setting access permissions
> 8. Additional Resources
>
> (a) Frequently Asked Questions (FAQ'S)
> (b) Mailing list support
> (c) Supplied documentation
> (d) Commercial support
> (e) Modifying the source code
>
> ---------------------------------------------------------------
>
> PostgreSQL Book Proposal
>
> Bruce Momjian
>
> 1.
> Introduction
> 2.
> Installation
> (a)
> Getting POSTGRESQL
> (b)
> Compiling
> (c)
> Initialization
> (d)
> Starting the server
> (e)
> Creating a database
> (f)
> Issuing database commands
> 3.
> Introduction to SQL
> (a)
> Why a database?
> (b)
> Creating tables
> (c)
> Adding data with INSERT
> (d)
> Viewing data with SELECT
> (e)
> Removing data with DELETE
> (f)
> Modifying data with UPDATE
> (g)
> Restriction with WHERE
> (h)
> Sorting data with ORDER BY
> (i)
> Usage of NULL values
> 4.
> Advanced SQL Commands
> (a)
> Inserting data from a SELECT
> (b)
> Aggregates: COUNT, SUM, etc.
> (c)
> GROUP BY with aggregates
> (d)
> HAVING with aggregates
> (e)
> Joining tables
> (f)
> Using table aliases
> (g)
> UNION clause
> (h)
> Subqueries
> (i)
> Transactions
> (j)
> Cursors
> (k)
> Indexing
> (l)
> Table defaults
> (m)
> Primary/Foreign keys
> (n)
> AND/OR usage
> (o)
> LIKE clause usage
> (p)
> Temporary tables
> (q)
> Importing data
> 5.
> POSTGRESQL'S Unique Features
> (a)
> Object ID'S (OID)
> (b)
> Multi-version Concurrency Control (MVCC)
> (c)
> Locking and Deadlocks
> (d)
> Vacuum
> (e)
> Views
> (f)
> Rules
> (g)
> Sequences
> (h)
> Triggers
> (i)
> Large Objects(BLOBS)
> (j)
> Adding User-defined Functions
> (k)
> Adding User-defined Operators
> (l)
> Adding User-defined Types
> (m)
> Exotic Preinstalled Types
> (n)
> Arrays
> (o)
> Inheritance
> 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)
> 7.
> POSTGRESQL Adminstration
> (a)
> Creating users and databases
> (b)
> Backup and restore
> (c)
> Performance tuning
> (d)
> Troubleshooting
> (e)
> Customization options
> (f)
> Setting access permissions
> 8.
> Additional Resources
> (a)
> Frequently Asked Questions (FAQ'S)
> (b)
> Mailing list support
> (c)
> Supplied documentation
> (d)
> Commercial support
> (e)
> Modifying the source code
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, maillist@candle.pha.pa.us, pgsql-hackers@postgreSQL.org, docs@postgreSQL.org
Subject: Re: [HACKERS] Outline for PostgreSQL book
In-Reply-To: <380408E9.9D4F554A@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