Re: Proposed patch for showing originating query on error
От | Dave Cramer |
---|---|
Тема | Re: Proposed patch for showing originating query on error |
Дата | |
Msg-id | A251E109-C390-4B9C-BF7C-100168D15E9C@fastcrypt.com обсуждение исходный текст |
Ответ на | Re: Proposed patch for showing originating query on error (Oliver Jowett <oliver@opencloud.com>) |
Ответы |
Re: Proposed patch for showing originating query on error
|
Список | pgsql-jdbc |
On 28-Jul-05, at 10:46 AM, Oliver Jowett wrote: > 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 Yeah, that would be cleaner. > - doing it only in execute() seems incomplete, there are other query > execution paths, perhaps this logic belongs somewhere in the query > executor? There are even more paths there to hook into. Putting it in AbstractJdbc2Statement minimizes the number of places it would need to be added to. QueryExecutor has a few Implementations ... > - ideally it should be configurable (hook it into whatever came out of > Kris' suggestions about including more info in server-generated > exception, perhaps?) Well, lets get it working first before we make it configurable. > > -O > >
В списке pgsql-jdbc по дате отправления: