On Fri, Jan 25, 2013 at 01:41:06PM -0500, Tom Lane wrote:
> Bruce Momjian <[email protected]> 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 <[email protected]> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
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;
</programlisting>
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; */
</programlisting>
The last form makes use of the variant referred to above as
character variable reference. You will see in later sections how C
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
