From: Oisin Glynn <me@oisinglynn.com>
To: pgsql general <pgsql-general@postgresql.org>
Cc: PostgreSQL Docs <pgsql-docs@postgresql.org>
Subject: Re: [DOCS] COPY command documentation
Date: Thu, 23 Mar 2006 15:31:42 -0500
Message-ID: <442305AE.4010507@oisinglynn.com> (raw)
In-Reply-To: <1143144857.17999.89.camel@state.g2switchworks.com>
References: <4422B9F8.60100@oisinglynn.com>
<483F344B-FF17-4DC5-8922-775213566788@pervasive.com>
<20060323201250.GC6106@fetter.org>
<1143144857.17999.89.camel@state.g2switchworks.com>
Scott Marlowe wrote:
> On Thu, 2006-03-23 at 14:12, David Fetter wrote:
>
>> On Thu, Mar 23, 2006 at 07:00:13PM +0100, Jim Nasby wrote:
>>
>>> On Mar 23, 2006, at 4:08 PM, Oisin Glynn wrote:
>>>
>>>
>>>> I just discovered that the comments from 8.0 had the answer I was
>>>> looking for but these comments are not in the 8.1 docs. Should the
>>>> comments be rolled forward as new versions are created? Or if valid
>>>> comments added to the docs themselves?
>>>>
>>>> http://www.postgresql.org/docs/8.1/interactive/sql-copy.html
>>>>
>>>> http://www.postgresql.org/docs/8.0/interactive/sql-copy.html
>>>>
>>> No, comments don't roll forward.
>>>
>> ...and it's unlikely that they will, now or later, without somebody
>> whose whole job is to monitor those comments and make patches.
>>
>> I'd like to make a Modest Proposalâ„¢: Let's take down the interactive
>> documents and, in their place, put up a request that doc patches be
>> sent to -docs.
>>
>
> Heck, why not a form that does it for somebody, takes their email
> address, and possibly even enrolls them in the -docs newsgroup. It
> can't be that hard to code up.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
I am a Windows only developer (for my sins) and to be honest we are
using postgres allot and are impressed by it but the *NIX centric
examples in the docs can sometimes be a challenge, if there is a clear
difference between Windows/*NIX operation and it is not obvious what the
Windows equivalent is then there should be a Windows example or a note
within the example explaining the difference.
It seems like the viewing docs with notes is far less useful if we loose
all the wisdom every time there is a new release, and personally I have
found the notes useful more than once.
Maybe a did you find this note useful button and useful notes get
priority for doc inclusion?
What is the process for submitting a doc patch? I am sure I should be
asking that on the doc list.
Oisin
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: me@oisinglynn.com, pgsql-general@postgresql.org
Subject: Re: [DOCS] COPY command documentation
In-Reply-To: <442305AE.4010507@oisinglynn.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