MySQL++

View Ticket
Login

View Ticket

2017-09-08
17:45 Closed ticket [4f077284dd]: Build failure against MariaDB 10.2.6 plus 6 other changes artifact: 432cac5812 user: tangent
2017-07-21
18:45 Ticket [4f077284dd]: 5 changes artifact: 0ebe356fe3 user: anonymous
2017-07-14
13:09 New ticket [4f077284dd]. artifact: 678d0084a6 user: anonymous

Ticket Hash: 4f077284dd2ca1b6230604862a826a6e674ca836
Title: Build failure against MariaDB 10.2.6
Status: Closed Type: Code Defect
Severity: Important Priority: Immediate
Subsystem: Library Resolution: Fixed
Last Modified: 2017-09-08 17:45:44
Version Found In: 3.2.2
User Comments:
anonymous added on 2017-07-14 13:09:16:
Trying to build MySQL++ 3.2.2 against MariaDB 10.2.6 causes a build failure:

./lib/dbdriver.cpp: In member function 'bool mysqlpp::DBDriver::set_option(unsigned int, bool)':
./lib/dbdriver.cpp:260:10: error: 'CLIENT_LONG_PASSWORD' was not declared in this scope
    (o >= CLIENT_LONG_PASSWORD) &&
          ^~~~~~~~~~~~~~~~~~~~
./lib/dbdriver.cpp:260:10: note: suggested alternative: 'CLIENT_LONG_FLAG'
    (o >= CLIENT_LONG_PASSWORD) &&
          ^~~~~~~~~~~~~~~~~~~~
          CLIENT_LONG_FLAG

In this new version of the MariaDB library, the CLIENT_LONG_PASSWORD flag was dropped. It was already marked as obsolete in previous versions of MariaDB.

Is it safe to just drop this test in MySQL++ code?

anonymous added on 2017-07-21 18:45:35:
Downstream (Fedora) bug: https://bugzilla.redhat.com/show_bug.cgi?id=1471139 . There's a patch from Augusto Caringi posted there:

https://bugzilla.redhat.com/attachment.cgi?id=1298334

which should fix this.

tangent added on 2017-09-08 17:45:44:
Fixed in [e5f2c3d83f].