diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2014-01-13 14:05:05 -0500 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2014-01-13 14:05:05 -0500 |
| commit | 1536bc4664a248faf81c62326fe1be3dbe18b8cd (patch) | |
| tree | 45fff52ffb650a24fea31d55ea17aab627893abe /doc | |
| parent | 5d973d52aa7d1e5b715ffb99800642cc2af4d972 (diff) | |
| download | sqlalchemy-1536bc4664a248faf81c62326fe1be3dbe18b8cd.tar.gz | |
- The MySQL CAST compilation now takes into account aspects of a string
type such as "charset" and "collation". While MySQL wants all character-
based CAST calls to use the CHAR type, we now create a real CHAR
object at CAST time and copy over all the parameters it has, so that
an expression like ``cast(x, mysql.TEXT(charset='utf8'))`` will
render ``CAST(t.col AS CHAR CHARACTER SET utf8)``.
- Added new "unicode returns" detection to the MySQL dialect and
to the default dialect system overall, such that any dialect
can add extra "tests" to the on-first-connect "does this DBAPI
return unicode directly?" detection. In this case, we are
adding a check specifically against the "utf8" encoding with
an explicit "utf8_bin" collation type (after checking that
this collation is available) to test for some buggy unicode
behavior observed with MySQLdb version 1.2.3. While MySQLdb
has resolved this issue as of 1.2.4, the check here should
guard against regressions. The change also allows the "unicode"
checks to log in the engine logs, which was not previously
the case. [ticket:2906]
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/build/changelog/changelog_09.rst | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/doc/build/changelog/changelog_09.rst b/doc/build/changelog/changelog_09.rst index 74f92da06..96f763e31 100644 --- a/doc/build/changelog/changelog_09.rst +++ b/doc/build/changelog/changelog_09.rst @@ -15,6 +15,33 @@ :version: 0.9.2 .. change:: + :tags: bug, mysql + + The MySQL CAST compilation now takes into account aspects of a string + type such as "charset" and "collation". While MySQL wants all character- + based CAST calls to use the CHAR type, we now create a real CHAR + object at CAST time and copy over all the parameters it has, so that + an expression like ``cast(x, mysql.TEXT(charset='utf8'))`` will + render ``CAST(t.col AS CHAR CHARACTER SET utf8)``. + + .. change:: + :tags: bug, mysql + :tickets: 2906 + + Added new "unicode returns" detection to the MySQL dialect and + to the default dialect system overall, such that any dialect + can add extra "tests" to the on-first-connect "does this DBAPI + return unicode directly?" detection. In this case, we are + adding a check specifically against the "utf8" encoding with + an explicit "utf8_bin" collation type (after checking that + this collation is available) to test for some buggy unicode + behavior observed with MySQLdb version 1.2.3. While MySQLdb + has resolved this issue as of 1.2.4, the check here should + guard against regressions. The change also allows the "unicode" + checks to log in the engine logs, which was not previously + the case. + + .. change:: :tags: bug, mysql, pool, engine :tickets: 2907 |