On Fri, 2006-05-19 at 13:11 +0200, Graham Leggett wrote: > This problem was solved by returning a simple APR error code, along with a > structure containing the LDAP error code, and the human readable error > string for logging.
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. -- Bojan
