Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TyoFD-0006vb-0S for pgsql-docs@arkaria.postgresql.org; Fri, 25 Jan 2013 18:43:19 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1TyoFB-0006pP-Uh for pgsql-docs@arkaria.postgresql.org; Fri, 25 Jan 2013 18:43:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TyoF2-0006hj-2j for pgsql-docs@postgresql.org; Fri, 25 Jan 2013 18:43:08 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TyoEx-0004I1-1B for pgsql-docs@postgresql.org; Fri, 25 Jan 2013 18:43:07 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1TyoEv-0005K5-MN; Fri, 25 Jan 2013 13:43:01 -0500 Date: Fri, 25 Jan 2013 13:43:01 -0500 From: Bruce Momjian To: Tom Lane Cc: Alan B , pgsql-docs@postgresql.org Subject: Re: Add clarification example to EXEC SQL CONNECT with password Message-ID: <20130125184301.GG6848@momjian.us> References: <20130125161942.GA6848@momjian.us> <14376.1359134732@sss.pgh.pa.us> <20130125172959.GB6848@momjian.us> <14933.1359136212@sss.pgh.pa.us> <20130125181921.GD6848@momjian.us> <16178.1359139266@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="48TaNjbzBVislYPb" Content-Disposition: inline In-Reply-To: <16178.1359139266@sss.pgh.pa.us> User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org --48TaNjbzBVislYPb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jan 25, 2013 at 01:41:06PM -0500, Tom Lane wrote: > Bruce Momjian 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. How is this? -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + --48TaNjbzBVislYPb Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="ecpg3.diff" diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml new file mode 100644 index bf01857..4d904cd *** a/doc/src/sgml/ecpg.sgml --- b/doc/src/sgml/ecpg.sgml *************** const char *passwd = "secret"; *** 198,205 **** EXEC SQL END DECLARE SECTION; ... EXEC SQL CONNECT TO :target USER :user USING :passwd; ! ! EXEC SQL CONNECT TO :target USER :user/:passwd; The last form makes use of the variant referred to above as character variable reference. You will see in later sections how C --- 198,204 ---- EXEC SQL END DECLARE SECTION; ... EXEC SQL CONNECT TO :target USER :user USING :passwd; ! /* or EXEC SQL CONNECT TO :target USER :user/:passwd; */ The last form makes use of the variant referred to above as character variable reference. You will see in later sections how C --48TaNjbzBVislYPb Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs --48TaNjbzBVislYPb--