From: nolan@celery.tssi.com
To: gearond@cvc.net
Cc: scrappy@postgresql.org
Cc: cobalt@bearfruit.org
Cc: pgsql-advocacy@postgresql.org
Subject: Re: [GENERAL] interesting PHP/MySQL thread
Date: Tue, 24 Jun 2003 00:07:32 -0500 (CDT)
Message-ID: <20030624050732.2523.qmail@celery.tssi.com> (raw)
In-Reply-To: <3EF7D23C.9040900@cvc.net>
> the new manuals seems to be drifting to using only GOOGLE listings.
> MUCH less information on one page, not nearly as good search results as
> the old one. I don't know why they are switching.
I think I must be old-fashioned, or perhaps just getting old, I think
online manuals are moving in the direction of becoming much harder for
me to use. (I have yet to master the 'info' format that Linux has
gone to, for example.)
And my pet peeve of the month is software source distributions that
include the documentation ONLY in HTML, which is OK IF you have Apache
running on the system you're building the sources on and are willing to
make the documentation directory available to Apache, but otherwise
they're very hard to use.
And while i'm on the subject, the only book (hard copy) I've got on
PostgreSQL is the O'Reilly 'Practical PostgreSQL' book, now a bit dated,
which has one of the worst indexes I've seen in a computer manual in years.
It may be the worst index I've ever experienced in an O'Reilly book.
(Sorry if Worsley or Drake are reading this, but that's my opinion.)
The O'Reilly Reese/Yarger/King/Williams MySQL book has a much more
comprehensive index, 23 pages compared to 7 for Worsley/Drake. I know
that indexes are the last thing authors want to do (both literally and
figuratively), but a good index makes the rest of the book much better.
I've had a series of paper clips, bulldog clips and post-it notes marking
the sections I tend to reuse frequently, because the index doesn't get
you there. Most of the time I use the online manual, and I've got a
few pages that aren't obvious from the table of contents bookmarked for
the online manual, too.
--
Mike Nolan
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: nolan@celery.tssi.com, gearond@cvc.net, scrappy@postgresql.org, cobalt@bearfruit.org, pgsql-advocacy@postgresql.org
Subject: Re: [GENERAL] interesting PHP/MySQL thread
In-Reply-To: <20030624050732.2523.qmail@celery.tssi.com>
* 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