Re: Proposed patch for showing originating query on error

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Oliver Jowett <oliver(at)opencloud(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:15:11
Message-ID: 8DBEB41D-35E7-4936-9D15-8D759C11E175@fastcrypt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc


On 28-Jul-05, at 11:06 AM, Oliver Jowett wrote:

> 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?
I'll give it some serious attention later, I hacked it in to your
code for someone, just wanted to get it into the discussion.
>
>
>>> - 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"
Agreed.
>
> -O
>
>

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Christian Cryder 2005-07-28 16:05:59 Re: smallint mapping issue
Previous Message Kevin Grittner 2005-07-28 15:13:21 Re: SQLException and error code