Using connection_created signal defined in django.db.backends.signalscauses maximum recursion depth reached runtime error.We fix this by not sending the extra signal after the connection tothe database is setup.Unit tests are updated.(cherry picked from commitc86a295)

Using prepared statements while inserting sufficiently largedata in a table with TEXT type column, data was getting corrupted.This was due to wrong encoding of data length while sendingprepared statement packet.We fix the issue by implementing a new function utils.lc_int().A unit test has been added for BUG#19522948.(cherry picked from commit12f82ab)

The type_code in cursor.description was not comparing equalto any of the type objects defined in mysql.connector.dbapi.We fix the issue by removing __cmp__ and implementing therich comparison operators for the PEP-249 classDBAPITypeObject.A unit test has been added for BUG#19584051.(cherry picked from commitf985cfc)

MySQL server 5.7.5 creates no user while bootstrapping a server. We addextra DML to create the root@ocalhost user, making sure unit test canrun.(cherry picked from commit062cbde)

Connector/Python Django backend was raising error while converting aninvalid datetime value instead of returning None. We fix this issueby adding a check for invalid values.Unit tests are updated.(cherry picked from commita57f885)

We fix Pylint W0633 warning in mysql.connector.network modulewith message "Attempting to unpack a non-sequence define at line 438".(cherry picked from commitd40192e)

We improve the errors reported when invalid sharding keysare given for RANGE_STRING and RANGE_DATETIME types.We additionally improve performance by moving the sortingof partition keys when saving cache entries. Previously, sortingwas done each time a partition was looked up.Unit test for BUG#19642249 was added in test_fabric module.(cherry picked from commita95e9c6)

Change user command raises packets out of order error when used withcompression. This causes error when a pooled connection tries toreset session which internally sends change user command for MySQLserver 5.7.2 or earlier. We fix this by raising a NotSupportedErrorwhenever someone tries to reset a session on MySQL server earlierthan 5.7.3.A test case has been added for BUG#19549363.(cherry picked from commit1b412b7)

We move the unit tests checking error code generation date from mainrepository to the internal repository. These tests need to be run onlywhile preparing release.(cherry picked from commitd86e4ba)

When connection character set is set to 'binary', the string datafailed to decode since it is not a valid Python character set.We fix this by returning string data without decoding when thecharacter set is set to 'binary'.A unit test has been added for BUG#19500097.(cherry picked from commitdcd5b63)

An extra patch in which we fix the Pylint errors for the theinsort_right_rev() function.(cherry picked from commit5454250)

We fix reporting errors containing non ascii characters withPython v2. We fix this by encoding error message with 'utf8'when used with Python v2.A unit test has been added for BUG#19803702.(cherry picked from commitc2a7630)

We fix lost connection to server error caused when serveris present at a remote location.

Using connection pooling with MySQL Fabric was raising AttributeError.We fix this by creating a pool of connections to a server as and whenfirst time it is required to be connected.To use pooling with Fabric, 'pool_size' argument should be used. Using'pool_name' with Fabric raises AttributeError. This is becausewe can't have two pools with same names on different servers.A unit test has been added for BUG#19331658.

The Connector/Python Django backend was creating too many databaseconnections since as soon as an object of DatabaseWrapper wasinstanciated, a connection to the MySQL server was set up. This isrequired to enable some version specific MySQL features.We fix this by adding the cached_property decorator to themysql_version()-method.Unit tests are updated and also fixes BUG#19954882.

We fix a SyntaxError introduced while pushing.

MySQLCursor.fetchwarnings() was not returning any warnings evenwhen warnings were generated by calling a stored procedure usingMySQLCursor.callproc() method. We add support to fetch warningsgenerated by a stored procedure.A unit test has been added for BUG#19777815.

Passwords consisting of only integers were raising error when usedwith option files. We fix this by not evaluating value for passwordoption in option files.Unit tests are updated.(cherry picked from commit677b310)

We this fix we support Django SafeText and SafeBytes type fields.A test case has been added for BUG#20106629.(cherry picked from commit18b69e4)

Inserting a string of length 251 to 255 using prepared statementswas raising a ProgrammingError exception:    1210 (HY000): Incorrect arguments to mysqld_stmt_executeWe fix this by correctly encoding the length of the string whilesending it to the server.A test case has been added for BUG#20407036.(cherry picked from commit955cfb7)

We fix conversion of SET data coming from MySQL serverwhen the set is empty. We now return an empty set(set([])) whichwas previously returned as a set of empty string(set([''])).A test case is added for BUG#20301989.(cherry picked from commitf9b22fa)

We fix receiving a large amount of data in a field from serverThe connector did not process packets correctly when distributedacross several packets.Also receiving text greater then 16777215 bytes raised anindex out of range error.A test case has been added for BUG#20462427.(cherry picked from commit7221b81)

We fix HASH based sharding which was causing the followingruntime error:    ValueError: Unsupported sharding type HASHA unit test has been added for BUG#20324089.(cherry picked from commit0f7a8e7)

Signed-off-by: Nuno Mariz <nuno.mariz@oracle.com>

This patch fixes a potential SQL injection that may occur whenthe parameters expansion is done in multiple steps and undersome circumstances a substring in an incoming parameter valuecan be expanded several times.