However, if an error is converted to another error along the way (DB throws an error, which is caught by DataObjects and repackaged to describe what DataObjects was trying to do), then there is no way currently to retrieve the old DB_Error from the DB_DataObject_Error.
I thought there was some backtrace stuff in pear error now, that should work for determining the source class of the error..
In theory, you should be able to stack errors.. - so that one error causes another one to be thrown from the wrapper.. - and then show a backtrace of them..
No idea if that is designed into PEAR error at present..
Regards
Alan
--
Can you help out?
Need Consulting Services or Know of a Job?
http://www.akbkhome.com