mysqlconnector cannot override settings
Issue #2515
resolved
In the mysqlconnector, the default setting for raise_on_warnings is set after the url string settings are read. This prevents the user from overriding the default setting if necessary.
Users who do not have '?raise_on_warnings=False' or '?buffered=False' in their url string will not notice any difference.
Comments (7)
-
repo owner
-
repo owner
- changed milestone to 0.x.xx
this is on hold as the current released and development versions of mysql-connector python are broken and non-functional with SQLAlchemy. See https://answers.launchpad.net/myconnpy/+question/209397 .
-
repo owner
the defaults just needed to be set correctly:
-
repo owner
-
repo owner
- changed status to open
this is wrong. "buffered" and "raise on warning" default to False. No clue why these are defaulitng to True.
-
repo owner
- edited description
- changed milestone to 1.0
-
repo owner
- changed status to resolved
- Changed the default value of "raise_on_warnings" to False for
MySQLconnector. This was set at True for some reason. The "buffered"
flag unfortunately must stay at True as MySQLconnector does not allow
a cursor to be closed unless all results are fully fetched. fixes
#2515 - lots of MySQL tests seemed to not be hitting all backends, so we should be getting some mysqlconnector failures now
→ <<cset 2b85e80d75f5>>
- Log in to comment
thanks