-
Notifications
You must be signed in to change notification settings - Fork 297
Master 2.0 #27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Master 2.0 #27
Conversation
Using connection_created signal defined in django.db.backends.signals causes maximum recursion depth reached runtime error. We fix this by not sending the extra signal after the connection to the database is setup. Unit tests are updated. (cherry picked from commit c86a295)
Using prepared statements while inserting sufficiently large data in a table with TEXT type column, data was getting corrupted. This was due to wrong encoding of data length while sending prepared 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 commit 12f82ab)
The type_code in cursor.description was not comparing equal to any of the type objects defined in mysql.connector.dbapi. We fix the issue by removing __cmp__ and implementing the rich comparison operators for the PEP-249 class DBAPITypeObject. A unit test has been added for BUG#19584051. (cherry picked from commit f985cfc)
MySQL server 5.7.5 creates no user while bootstrapping a server. We add extra DML to create the root@ocalhost user, making sure unit test can run. (cherry picked from commit 062cbde)
Connector/Python Django backend was raising error while converting an invalid datetime value instead of returning None. We fix this issue by adding a check for invalid values. Unit tests are updated. (cherry picked from commit a57f885)
We fix Pylint W0633 warning in mysql.connector.network module with message "Attempting to unpack a non-sequence define at line 438". (cherry picked from commit d40192e)
We improve the errors reported when invalid sharding keys are given for RANGE_STRING and RANGE_DATETIME types. We additionally improve performance by moving the sorting of partition keys when saving cache entries. Previously, sorting was done each time a partition was looked up. Unit test for BUG#19642249 was added in test_fabric module. (cherry picked from commit a95e9c6)
Change user command raises packets out of order error when used with compression. This causes error when a pooled connection tries to reset session which internally sends change user command for MySQL server 5.7.2 or earlier. We fix this by raising a NotSupportedError whenever someone tries to reset a session on MySQL server earlier than 5.7.3. A test case has been added for BUG#19549363. (cherry picked from commit 1b412b7)
We move the unit tests checking error code generation date from main repository to the internal repository. These tests need to be run only while preparing release. (cherry picked from commit d86e4ba)
When connection character set is set to 'binary', the string data failed to decode since it is not a valid Python character set. We fix this by returning string data without decoding when the character set is set to 'binary'. A unit test has been added for BUG#19500097. (cherry picked from commit dcd5b63)
An extra patch in which we fix the Pylint errors for the the insort_right_rev() function. (cherry picked from commit 5454250)
We fix reporting errors containing non ascii characters with Python 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 commit c2a7630)
We fix lost connection to server error caused when server is 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 when first 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 because we 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 database connections since as soon as an object of DatabaseWrapper was instanciated, a connection to the MySQL server was set up. This is required to enable some version specific MySQL features. We fix this by adding the cached_property decorator to the mysql_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 even when warnings were generated by calling a stored procedure using MySQLCursor.callproc() method. We add support to fetch warnings generated by a stored procedure. A unit test has been added for BUG#19777815.
Passwords consisting of only integers were raising error when used with option files. We fix this by not evaluating value for password option in option files. Unit tests are updated. (cherry picked from commit 677b310)
We this fix we support Django SafeText and SafeBytes type fields. A test case has been added for BUG#20106629. (cherry picked from commit 18b69e4)
Inserting a string of length 251 to 255 using prepared statements was raising a ProgrammingError exception: 1210 (HY000): Incorrect arguments to mysqld_stmt_execute We fix this by correctly encoding the length of the string while sending it to the server. A test case has been added for BUG#20407036. (cherry picked from commit 955cfb7)
We fix conversion of SET data coming from MySQL server when the set is empty. We now return an empty set(set([])) which was previously returned as a set of empty string(set([''])). A test case is added for BUG#20301989. (cherry picked from commit f9b22fa)
We fix receiving a large amount of data in a field from server The connector did not process packets correctly when distributed across several packets. Also receiving text greater then 16777215 bytes raised an index out of range error. A test case has been added for BUG#20462427. (cherry picked from commit 7221b81)
We fix HASH based sharding which was causing the following runtime error: ValueError: Unsupported sharding type HASH A unit test has been added for BUG#20324089. (cherry picked from commit 0f7a8e7)
Signed-off-by: Nuno Mariz <nuno.mariz@oracle.com>
This patch fixes a potential SQL injection that may occur when the parameters expansion is done in multiple steps and under some circumstances a substring in an incoming parameter value can be expanded several times.
Hi, thank you for submitting this pull request. In order to consider your code we need you to sign the Oracle Contribution Agreement (OCA). Please review the details and follow the instructions at http://www.oracle.com/technetwork/community/oca-486395.html |
Hi, there was no response to our request to sign an OCA or confirm the code is submitted under the terms of the OCA. As such this request will be closed. |
No description provided.