From: Gord Thompson <gord@gordthompson.com>
Date: Wed, 4 Dec 2019 00:41:56 +0000 (-0700)
Subject: Add note re: using the MySQL ODBC "ANSI" driver for mysql+pyodbc.
X-Git-Tag: rel_1_4_0b1~592^2~1
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=9592a7afccc5ed0a245b0fca6ad34e748a38336a;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

Add note re: using the MySQL ODBC "ANSI" driver for mysql+pyodbc.
---

diff --git a/lib/sqlalchemy/dialects/mysql/pyodbc.py b/lib/sqlalchemy/dialects/mysql/pyodbc.py
index 0da5a8eafc..c533595bbe 100644
--- a/lib/sqlalchemy/dialects/mysql/pyodbc.py
+++ b/lib/sqlalchemy/dialects/mysql/pyodbc.py
@@ -14,11 +14,16 @@
     :connectstring: mysql+pyodbc://<username>:<password>@<dsnname>
     :url: http://pypi.python.org/pypi/pyodbc/
 
-    .. note:: The PyODBC for MySQL dialect is not well supported, and
-       is subject to unresolved character encoding issues
-       which exist within the current ODBC drivers available.
-       (see http://code.google.com/p/pyodbc/issues/detail?id=25).
-       Other dialects for MySQL are recommended.
+.. note::
+
+    The PyODBC for MySQL dialect is **not tested as part of
+    SQLAlchemy's continuous integration**.
+    The recommended MySQL dialects are mysqlclient and PyMySQL.
+    However, if you want to use the mysql+pyodbc dialect and require
+    full support for ``utf8mb4`` characters (including supplementary
+    characters like emoji) be sure to use a current release of
+    MySQL Connector/ODBC and specify the "ANSI" (**not** "Unicode")
+    version of the driver in your DSN or connection string.
 
 """