Skip site navigation (1) Skip section navigation (2)

quick ECPG doco change

From: Philip Yarra <philip(at)utiba(dot)com>
To: pgsql-interfaces(at)postgresql(dot)org
Subject: quick ECPG doco change
Date: 2003-11-19 00:00:34
Message-ID: 200311191100.34246.philip@utiba.com (view raw or flat)
Thread:
Lists: pgsql-interfaces
Hi, this doco patch is a quick one to add explicit mention of the need for the 
AT clause in threaded ECPG applications. Does this sound okay?

Bruce, yes, I do intend to contribute more than this, but at least this will
stop some confusion in the meantime.

Regards, Philip Yarra.


Index: ecpg.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql-server/doc/src/sgml/ecpg.sgml,v
retrieving revision 1.54
diff -c -r1.54 ecpg.sgml
*** ecpg.sgml   12 Nov 2003 22:47:47 -0000      1.54
--- ecpg.sgml   18 Nov 2003 23:20:51 -0000
***************
*** 353,358 ****
--- 353,365 ----
  </programlisting>
     This option is particularly suitable if the application needs to
     use several connections in mixed order.
+       </para>
+
+       <para>
+       If your application uses multiple threads of execution, they cannot
share a
+       connection concurrently. You must either explicitly control access to
the connection
+       (using mutexes) or use a connection for each thread. If each thread
uses its own connection,
+       you will need to use the AT clause to specify which connection the
thread will use.
    </para>

    <para>

-------------------------------------------------------


Responses

pgsql-interfaces by date

Next:From: Markus SeiboldDate: 2003-11-21 13:48:22
Subject: Open source data modeling tools for PostgreSQL
Previous:From: Frank SchourenDate: 2003-11-18 14:43:14
Subject: FW: PostgreSQL - mySAP

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group