Forum Moderators: coopster
So, let's say there are 3 different query statements being processed and I want to know which is failing. If I monitor for the error in the class method itself, I am not going to find out much unless I dump that particular statement as part of the error. Then I can go back in the code and figure out which statement it is (usually).
However, if I were to process the statement and set an overall class error and monitor for that error upon return of the invoked method, I can now tell which file, line, etc the error was trapped at. Very similar to what you see in PEAR's error-monitoring routines.