On Mon, Feb 21, 2005 at 09:17:03PM -0500, Garrett Rooney wrote: > I agree, it would be good to do something about that. You might want to > look at how the ldap API handles this kind of thing. If I recall > correctly they've got some sort of error object they return which in our > case could contain both underlying database error codes, a standardized > APR error code, etc. > Something like that would certainly be preferable - in the general case standard error messages might be fine, but we'd be missing a lot of useful info if there was no way to access the raw error.
vh Mads Toftum -- `Darn it, who spiked my coffee with water?!' - lwall
