Re: Add clarification example to EXEC SQL CONNECT with password

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Alan B <alan77codebits(at)gmail(dot)com>, pgsql-docs(at)postgresql(dot)org
Subject: Re: Add clarification example to EXEC SQL CONNECT with password
Date: 2013-01-25 18:41:06
Message-ID: 16178.1359139266@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Fri, Jan 25, 2013 at 12:50:12PM -0500, Tom Lane wrote:
>> (looks at the whole section) As-is, it's definitely not good, because
>> before there were three independent examples, and now there are three
>> and a half --- the added example depends on the variables declared in
>> the third example. But using the blank line means you've formatted it
>> as a stand-alone fourth example, which is not only wrong in itself but
>> it screws up the meanings of both of the subsequent paragraphs.

> OK, how is this? The C comment allows me to add 'or'.

It's still completely failing to address the problem that it's formatted
as a fourth, independent example. Please remove the blank line.

regards, tom lane

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2013-01-25 18:43:01 Re: Add clarification example to EXEC SQL CONNECT with password
Previous Message Bruce Momjian 2013-01-25 18:19:21 Re: Add clarification example to EXEC SQL CONNECT with password