summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorMichael Meskes2017-06-06 10:19:28 +0000
committerMichael Meskes2017-06-06 10:20:31 +0000
commit0f33ee0e3b7527fb0c88abf0ae8a49a9c38d9c0e (patch)
tree8db328593404a81f9978b4b8876056683419664b /doc/src
parentc1abe6c786d8f00643de8519140d77644b474163 (diff)
Fix docs to not claim ECPG's SET CONNECTION is not thread-aware.
Changed by: Tsunakawa, Takayuki <tsunakawa.takay@jp.fujitsu.com>
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/ecpg.sgml5
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml
index dead4c3f86..f13a0e999f 100644
--- a/doc/src/sgml/ecpg.sgml
+++ b/doc/src/sgml/ecpg.sgml
@@ -240,8 +240,7 @@ EXEC SQL AT <replaceable>connection-name</replaceable> SELECT ...;
<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.
+ (using mutexes) or use a connection for each thread.
</para>
<para>
@@ -251,7 +250,7 @@ EXEC SQL AT <replaceable>connection-name</replaceable> SELECT ...;
EXEC SQL SET CONNECTION <replaceable>connection-name</replaceable>;
</programlisting>
This option is particularly convenient if many statements are to be
- executed on the same connection. It is not thread-aware.
+ executed on the same connection.
</para>
<para>