Hi, this doco patch is a quick one to add explicit mention of the need

for the AT clause in threaded ECPG applications.

Philip Yarra

diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml
index 2c113385de1226c215cf5ce1e6de7c279d7dcf42..27aca4e60eaab1e46dd071ece708e29616c89a95 100644 (file)
--- a/doc/src/sgml/ecpg.sgml
+++ b/doc/src/sgml/ecpg.sgml
@@ -1,5 +1,5 @@
 
 
 
@@ -353,6 +353,13 @@ EXEC SQL AT connection-name SELECT ...;
 
    This option is particularly suitable if the application needs to
    use several connections in mixed order.
+      
+
+      
+      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.