On 1/2/2014 10:04, Jake Colman wrote:
That part of MySQL++ is not really a "public" API. It exists for
MySQL++'s own needs. Since MySQL++ doesn't have specific support for
these types -- there is no MySQL++ bit type, or a "geometry" type, or...
-- it doesn't reference those enum values.
MySQL++ doesn't provide 100% coverage of the entire MySQL C API, it
never claimed to, and there isn't even a stated goal that this gap is to
be driven to 0. MySQL++ only provides facilities that someone with
drive and ability wrote.
If this gap bothers you, patches are always thoughtfully considered.