On Thu, 11 Feb 1999, Bob Dusek wrote:
The problem with writing a book on Postgres is that it's still
being developed. Before a book could be published, it'd be mostly
obsolete. I certainly would like the exercise of assembling one, but I
really hate getting obsolete books. This happened to me when I bought my
first Java book. I took it home and almost nothing in it worked. :) Of
course, Postgres is changing in a compatible way, but the new stuff that's
introduced *dramatically* changes the way people code. pl/pgsql is a
great example of this. There's stuff that's done in pl/pgsql that
previously had to be done C in a really complicated way, or you had to sit
around wishing for. This will change yet again when there's fk/pk
constraints and such. Chances are, there'll be a lot of neat stuff that
will need to be included in a book before a book can be finished. :)
I'm sure there's enough documentation lying around to make a
decent book if we want to put it together. Figuring out royalties could
be kinda difficult. :)
// Amen. A book would be really cool. I would think that it would open up
// the PostgreSQL market a bit more, too. A book on the shelf is
// advertising.
//
// A new, good, recommended book is great advertising.
//
// Bob
//
// On Thu, 11 Feb 1999, Robert Chalmers wrote:
//
// > Just wondering if there is a book specifically written around PgSQL, and if not, would anyone want one? You know,
athing like "A Guide To PgSQL". Not too heavy, maybe in parts. User + Advanced + ODBC ?
// >
// > What do you think?
// >
// > Robert
// >
//
//
//
--
Principal Member Technical Staff, beyond.com The world is watching America,
pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.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. __
