The commit message for the change that addressed this notes
- SET_CLIENT_STMT_ERROR now maps to stmt_set_error and accepts variadic arguments
This does have the side effect (not sure if it's intended or not) of now requiring the C++11 standard (previously the client could be used with C++03 but variadic argument usage breaks that) in order to compile cleanly (and break builds where warnings are treated as errors)
As I noted, I'm not sure if this is intentional or not, but if so perhaps the new C++ language requirement for the client should be noted.
The commit message for the change that addressed this notes
This does have the side effect (not sure if it's intended or not) of now requiring the C++11 standard (previously the client could be used with C++03 but variadic argument usage breaks that) in order to compile cleanly (and break builds where warnings are treated as errors)
As I noted, I'm not sure if this is intentional or not, but if so perhaps the new C++ language requirement for the client should be noted.