Re: blatantly a bug in the documentation - Mailing list pgsql-hackers

From Dave Page
Subject Re: blatantly a bug in the documentation
Date
Msg-id 937d27e10811240607q66bcfd1av14daddc4bca21d6f@mail.gmail.com
Whole thread Raw
In response to Re: blatantly a bug in the documentation  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: blatantly a bug in the documentation  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Mon, Nov 24, 2008 at 2:02 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>> Dave Page wrote:
>>> It might also be useful to create such a database at initdb time so
>>> newbies have something interesting to look at right away.
>
>> No, there is no need to clutter every installation in the world with
>> such a database. You could make it an addon module, or a pgfoundry project.
>
> The whole thing strikes me as extreme overkill, not to mention a
> misunderstanding of what an example is supposed to be for.  If we're
> going to insist that every example in the docs work when
> copied-and-pasted into an empty database, then simple and to-the-point
> examples will be history.  Instead of one-liners we'll have clutter.

That's the point of having a sample database ready to play with. The
docs needn't have clutter, but the user can try out any of the
examples without needing to setup anything first. It's a simple
usability tweak that can help ease the learning curve for new users.


-- 
Dave Page
EnterpriseDB UK:   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: blatantly a bug in the documentation
Next
From: Magnus Hagander
Date:
Subject: Re: [COMMITTERS] pgsql: Explicitly bind gettext() to the UTF8 locale when in use.