On Fri, May 19, 2006 1:17 pm, Bojan Smojver wrote: > Yep. All we need to do is return consistent APR error codes from DBD > functions, which is something we aren't doing right now. We already have > a way of getting the underlying error codes and descriptions via native > handles or provided DBD functions.
In the LDAP code, there was a choice between providing functions to look up code strings, or to just return the code strings regardless at the end of the call and be done with it. As the code string lookups were cheap, and only done on the error case, it meant that a programmer was more likely to make the info available rather than just writing out the (useless) APR code to the end user. Regards, Graham --
