Re: Proposed patch for showing originating query on error

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Dave Cramer <pg(at)fastcrypt(dot)com>
Cc: List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Proposed patch for showing originating query on error
Date: 2005-07-28 15:06:48
Message-ID: 42E8F488.6070704@opencloud.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Dave Cramer wrote:

> 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 ...

Well, do you have a better suggestion that catches all paths?

>> - 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.

sigh :( let's get it right before we commit it at all.. in practise it
seems "we'll fix this later" means "we won't fix it"

-O

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kevin Grittner 2005-07-28 15:13:21 Re: SQLException and error code
Previous Message Dave Cramer 2005-07-28 14:55:12 Re: Proposed patch for showing originating query on error