Bojan Smojver <[EMAIL PROTECTED]> wrote:
> Yeah, that's a problem throughout DBD at the moment. Basically, I was  
> just following what we do in other drivers - return database specific  
> non-zero return code to the caller. It sucks. Maybe if muster enough  
> courage, I may even fix that in all drivers and documentation (don't  
> hold your breath :-).

        That would kick ass. The "P" stands for portability, right? :-)

        Looking through the existing status codes, it looks like returning
"APR_ENOMEM" would be best.

        Cheers,
                Tyler

Reply via email to