Details
-
Bug
-
Resolution: Done
-
P3: Somewhat important
-
6.2.0
-
None
-
-
11f5c07c1b312d70197bbada3842d72c1c97c5ff (qt/qtbase/dev) 69080ce332cef9a405c38d298319de00c9e2dfd8 (qt/qtbase/6.2.1) 3b2c6b714736c075185c06fd701ace2535fc588e (qt/qtbase/6.2)
Description
Function QSqlDatabase.open() prints warning:
"MySQL: Unable to set the client character set to utf8 (""). Using 'utf8' instead.".
Tried to use wrong password and got a warning:
MySQL: Unable to set the client character set to utf8 ("Access denied for user 'lsserver'@'localhost' (using password: YES)"). Using 'utf8' instead.
Attachments
For Gerrit Dashboard: QTBUG-97054 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
376800,2 | MySQL: fix the check for the return value of mysql_set_character_set() | dev | qt/qtbase | Status: MERGED | +2 | 0 |
376801,2 | MySQL: only set the charset if the connection has succeeded | dev | qt/qtbase | Status: MERGED | +2 | 0 |
377453,2 | MySQL: fix the check for the return value of mysql_set_character_set() | 6.2 | qt/qtbase | Status: MERGED | +2 | 0 |
377454,2 | MySQL: fix the check for the return value of mysql_set_character_set() | 6.2.1 | qt/qtbase | Status: MERGED | +2 | 0 |
377455,4 | MySQL: only set the charset if the connection has succeeded | 6.2 | qt/qtbase | Status: MERGED | +2 | 0 |
377456,1 | MySQL: only set the charset if the connection has succeeded | 6.2.1 | qt/qtbase | Status: ABANDONED | 0 | 0 |