You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/content/connection-options.md
+6-1Lines changed: 6 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
lastmod: 2021-02-06
2
+
lastmod: 2021-11-25
3
3
date: 2016-10-16
4
4
title: Connection Options
5
5
customtitle: MySQL Connection String for C# .NET Core Programs
@@ -390,6 +390,11 @@ These are the other options that MySqlConnector supports. They are set to sensib
390
390
<td>false</td>
391
391
<td>When set to <code>false</code> or no (strongly recommended), security-sensitive information, such as the password, is not returned as part of the connection string if the connection is open or has ever been in an open state. Resetting the connection string resets all connection string values, including the password. Recognized values are true, false, yes, and no.</td>
392
392
</tr>
393
+
<trid="Pipelining">
394
+
<td>Pipelining</td>
395
+
<td>true</td>
396
+
<td>When set to <code>true</code>, queries will be "pipelined" (when possible) by sending multiple packets to the server before waiting for a response. This improves performance (by reducing latency) but is not compatible with some servers (most notably Amazon Aurora RDS). Set to <code>false</code> to disable this behavior.</td>
The cause of this problem is Amazon Aurora not correctly supporting pipelining in the MySQL protocol. This is known to be a problem with 2.x versions of Aurora (that implement MySQL 5.7), but not with 3.x versions (that implement MySQL 8.0).
20
+
21
+
To work around it, add `Pipelining = False;` to your connection string to disable the pipelining feature.
0 commit comments