Bug #87337 | 8.0.2 reintroduces my_bool to client API | ||
---|---|---|---|
Submitted: | 7 Aug 2017 8:18 | Modified: | 21 Aug 2017 19:35 |
Reporter: | Alexey Kopytov | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: C API (client library) | Severity: | S3 (Non-critical) |
Version: | 8.0.2 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[7 Aug 2017 8:18]
Alexey Kopytov
[7 Aug 2017 9:06]
MySQL Verification Team
Hello Alexey, Thank you for the report and feedback. Thanks, Umesh
[8 Aug 2017 12:28]
Tor Didriksen
Posted by developer: Fixed by patch for internal bug: commit 606b344a671a56ffa52939fdb3182a0450fd101f Author: Steinar H. Gunderson <steinar.gunderson@oracle.com> Date: Tue Aug 8 10:43:35 2017 +0200 Bug #26588846: MYSQL CUSTOM TYPES LEAK INTO THE CLIENT NAMESPACE Since WL#8020, we now leak MySQL-specific typedefs (uchar, my_bool, etc.) into the client namespace when including mysql.h. This is bound to cause problems for users sooner or later, and also reintroduces the dreaded my_bool type. Get rid of them again. Change-Id: Ie2358999558f61b1a501884388cd6ae7f07770d8
[21 Aug 2017 19:35]
Paul DuBois
Posted by developer: Fixed in 8.0.3. MySQL-specific typedefs such as uchar and my_bool were inadvertently reintroduced into the client namespace if the mysql.h header file was included.