diff options
author | Mike Bayer <mike_mp@zzzcomputing.com> | 2019-01-13 18:15:52 -0500 |
---|---|---|
committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2019-01-15 10:04:09 -0500 |
commit | c0e6ebd70b04c7941b7750c77cd4329b043679f8 (patch) | |
tree | e109d1fc5a7fb3db2f26525a8e66d14e00f7c7e5 /lib/sqlalchemy/dialects/postgresql/psycopg2.py | |
parent | b229a50c7786d8cbe65a2bf471b57a806f4259e3 (diff) | |
download | sqlalchemy-c0e6ebd70b04c7941b7750c77cd4329b043679f8.tar.gz |
Render N'' for SQL Server unicode literals
The ``literal_processor`` for the :class:`.Unicode` and
:class:`.UnicodeText` datatypes now render an ``N`` character in front of
the literal string expression as required by SQL Server for Unicode string
values rendered in SQL expressions.
Note that this adds full unicode characters to the standard test suite,
which means we also need to bump MySQL provisioning up to utf8mb4.
Modern installs do not seem to be reproducing the 1271 issue locally,
if it reproduces in CI it would be better for us to skip those ORM-centric
tests for MySQL.
Also remove unused _StringType from SQL Server dialect
Fixes: #4442
Change-Id: Id55817b3e8a2d81ddc8b7b27f85e3f1dcc1cea7e
Diffstat (limited to 'lib/sqlalchemy/dialects/postgresql/psycopg2.py')
0 files changed, 0 insertions, 0 deletions