postgres.git / summary / log / commit / refs

commit    dc33b0961eb9628290c29f465ef416c8991a3f0c
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Fri Jan 25 16:18:44 2013 +0000
First released in: 9.3.0, 9.2.3

    docs:  In ecpg, clarify how username/password colon parameters are used
    
    Backpatch to 9.2.
    
    Patch from Alan B


 doc/src/sgml/ecpg.sgml | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml
index 63aaf89b87f..bf01857a4c2 100644
--- a/doc/src/sgml/ecpg.sgml
+++ b/doc/src/sgml/ecpg.sgml
@@ -194,9 +194,12 @@ EXEC SQL CONNECT TO unix:postgresql://sql.mydomain.com/mydb AS myconnection USER
 EXEC SQL BEGIN DECLARE SECTION;
 const char *target = "mydb@sql.mydomain.com";
 const char *user = "john";
+const char *passwd = "secret";
 EXEC SQL END DECLARE SECTION;
  ...
-EXEC SQL CONNECT TO :target USER :user;
+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


[parent: a33c0045a86d]