Dave Cramer wrote:
> This just adds an exception to the existing backend exception showing
> the originating query.
I think the basic idea is ok, but..
- this should be on the original exception, not on a chained synthetic
exception
- doing it only in execute() seems incomplete, there are other query
execution paths, perhaps this logic belongs somewhere in the query executor?
- ideally it should be configurable (hook it into whatever came out of
Kris' suggestions about including more info in server-generated
exception, perhaps?)
-O
