]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
Render N'' for SQL Server unicode literals
authorMike Bayer <mike_mp@zzzcomputing.com>
Sun, 13 Jan 2019 23:15:52 +0000 (18:15 -0500)
committerMike Bayer <mike_mp@zzzcomputing.com>
Tue, 15 Jan 2019 15:04:09 +0000 (10:04 -0500)
commitc0e6ebd70b04c7941b7750c77cd4329b043679f8
treee109d1fc5a7fb3db2f26525a8e66d14e00f7c7e5
parentb229a50c7786d8cbe65a2bf471b57a806f4259e3
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
doc/build/changelog/unreleased_13/4442.rst [new file with mode: 0644]
lib/sqlalchemy/dialects/mssql/base.py
lib/sqlalchemy/testing/provision.py
lib/sqlalchemy/testing/requirements.py
lib/sqlalchemy/testing/suite/test_types.py
setup.cfg
test/dialect/mssql/test_types.py
test/requirements.py