On Sat, 2009-10-10 at 10:55 +0400, Kevac Marko wrote: > For example, we are using information from MYSQL_FIELD structure, > which, again, is not available from apr_dbd.h functions. Anyway, with > some dark "hack" magic one can access it (of course in non-portable > manner).
I'm guessing you are getting the handle directly with apr_dbd_native_handle() and then executing MySQL calls on it, right? > Variable max_length in MYSQL_FIELD is not populated for prepared > statements without flag in patch. This is why we need it. Normally, the driver will contain stuff it needs in order to satisfy its own API. If you are using hacks to get to MySQL stuff, maybe you can set STMT_ATTR_UPDATE_MAX_LENGTH directly after getting the prepared statement using another hack? -- Bojan
