From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, "A(dot) Kretschmer" <andreas(dot)kretschmer(at)schollglas(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: blatantly a bug in the documentation |
Date: | 2008-11-24 13:53:00 |
Message-ID: | 492AB1BC.4070705@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dave Page wrote:
> On Mon, Nov 24, 2008 at 1:38 PM, Alvaro Herrera
> <alvherre(at)commandprompt(dot)com> wrote:
>
>> A. Kretschmer wrote:
>>
>>
>>> Okay, it is an argument. On the other side, it was a question today in
>>> the irc-channel (#postgresql) today, someone asked, why his funktion
>>> don't work. I think, such examples should not contain such code. It is
>>> not apparent that this function are not available.
>>>
>> Perhaps the whole chapter could be improved if all the examples referred
>> to a set of tables and functions previously defined in the introduction
>> of the chapter. It would be good if the user could cut'n paste the code
>> and try it out directly, instead of having to reverse engineer the
>> tables/columns used for each example (and they're quite inconsistent).
>> Also, some examples give the complete code including CREATE FUNCTION and
>> others don't.
>>
>
> 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.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | A. Kretschmer | 2008-11-24 13:53:07 | Re: blatantly a bug in the documentation |
Previous Message | Alvaro Herrera | 2008-11-24 13:52:13 | Re: Snapshot warning |