summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/dialects/mysql/pymysql.py
Commit message (Collapse)AuthorAgeFilesLines
* - Fixed unicode support for PyMySQL when using an "executemany"Mike Bayer2015-03-221-0/+5
| | | | | | | | | operation with unicode parameters. SQLAlchemy now passes both the statement as well as the bound parameters as unicode objects, as PyMySQL generally uses string interpolation internally to produce the final statement, and in the case of executemany does the "encode" step only on the final statement. fixes #3337
* - more updates to the unicode mess to frame this inMike Bayer2015-03-221-3/+3
| | | | as up-to-date recommendations as possible
* - reorganize MySQL docs re: unicode, other cleanup and updatesMike Bayer2015-03-201-0/+6
|
* - copyright 2015Mike Bayer2015-03-101-1/+1
|
* - Updated the "supports_unicode_statements" flag to True for MySQLdbMike Bayer2014-12-041-2/+1
| | | | | | | | | and Pymysql under Python 2. This refers to the SQL statements themselves, not the parameters, and affects issues such as table and column names using non-ASCII characters. These drivers both appear to support Python 2 Unicode objects without issue in modern versions. fixes #3121
* - apply pep8 formatting to sqlalchemy/sql, sqlalchemy/util, sqlalchemy/dialects,Brian Jarrett2014-07-201-4/+5
| | | | sqlalchemy/orm, sqlalchemy/event, sqlalchemy/testing
* - break up the <authors> copyright comment as part of a passMike Bayer2014-07-091-1/+2
| | | | to get all flake8 passing
* - Fixed bug which prevented MySQLdb-based dialects (e.g.Mike Bayer2014-02-031-0/+1
| | | | | | | | | | pymysql) from working in Py3K, where a check for "connection charset" would fail due to Py3K's more strict value comparison rules. The call in question wasn't taking the database version into account in any case as the server version was still None at that point, so the method overall has been simplified to rely upon connection.character_set_name(). [ticket:2933]
* - happy new yearMike Bayer2014-01-051-1/+1
|
* - Improvements to the operation of the pymysql dialect onMike Bayer2013-04-211-12/+8
| | | | | | | | Python 3, including some important decode/bytes steps. Issues remain with BLOB types due to driver issues. Courtesy Ben Trofatter. - start using util.py3k, we will eventually remove the sa2to3 fixer entirely
* Added workaround for pymysql3 double wrapping ProgrammingErrors to pymysql ↵Ben Trofatter2013-03-181-0/+12
| | | | | | dialect. Added workaround for pymysql3 return a bytes object when queried for isolation level.
* happy new year (see #2645)Diana Clarke2013-01-011-1/+1
|
* kill me now, pep8 pass, so closeDiana Clarke2012-11-201-1/+2
|
* juts a 'expected 2 blank lines' pep8 passDiana Clarke2012-11-191-0/+1
|
* - rework the sphinx customizations into distinct modulesMike Bayer2012-10-191-14/+6
| | | | | | | - build a new Sphinx extension that allows dialect info to be entered as directives which is then rendered consistently throughout all dialect/dbapi sections - break out the "empty_strings" requirement for oracle test
* - move out maxdbMike Bayer2012-10-181-0/+3
| | | | | | - begin consolidating docs for dialects to be more self contained - add a separate section for "external" dialects - not sure how we're going to go with this yet.
* more import cleanupsMike Bayer2012-08-071-1/+1
|
* trailing whitespace bonanzaMike Bayer2012-07-281-8/+8
|
* happy new yearMike Bayer2012-01-041-1/+1
|
* - [bug] Unicode adjustments allow latest pymysqlMike Bayer2011-11-021-0/+1
| | | | (post 0.4) to pass 100% on Python 2.
* - New DBAPI support for pymysql, a pure Python portMike Bayer2011-01-261-0/+38
of MySQL-python. [ticket:1991]
View Lorry Controller Status