From: Bruce Momjian <maillist@candle.pha.pa.us>
To: Hannu Krosing <hannu@trust.ee>
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 07:20:13 -0400 (EDT)
Message-ID: <199910131120.HAA02994@candle.pha.pa.us> (raw)
In-Reply-To: <3804545B.FC9376E8@trust.ee>
> And perhaps some discussion about Date/Time types also in the section
> for programming languages (what you get from date field, how to be
> sure that what you give to postgresql is understood correctly)
>
> > The most important thing is to have alot of samples.
> > Practical samples are more useful than just syntax.
>
> Agreed.
>
> Maybe "Advanced SQL Commands" could also contain:
>
> * Outer Joins
But we don't have them yet.
> * Casts (bot AS and ::, with some explanations on why and when)
>
> Not sure if Views and Triggers should go under Uniqe features - they are
> supported on most commercial SQL databases.
Yes, I know, but Triggers are specific to the database, and I guess I
have to move views to the other section.
>
> "Interfacing to the POSTGRESQL Database" could also contain more options
> than PHP,
> at least as references - there are much more of both established (CGI,
> PyApache,mod_perl)
That's probably too advanced for this book. Not sure how much detail I
am going to give each interface anyway. Probably just two examples of
each.
> and emerging (like the recent pgxml announcement) technologies for that
> purpos.
>
> Server side programming should also mention PL/Tcl
>
Added.
> Under which section would requirements the restrictions (db size, field
> size/count, record size/count)
> or lackof them :) go?
Under Administration, or Installation.
--
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
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: maillist@candle.pha.pa.us, hannu@trust.ee, pgsql-hackers@postgreSQL.org, docs@postgreSQL.org
Subject: Re: [HACKERS] Outline for PostgreSQL book
In-Reply-To: <199910131120.HAA02994@candle.pha.pa.us>
* 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