Re: getting async raise notice messages

Hi Pawel,

Got it, thanks for the explanation

Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca

On 28 January 2015 at 14:55, Pawel Veselov <pawel(dot)veselov(at)gmail(dot)com> wrote:

>
> Hi Dave.
>
> On Wed, Jan 28, 2015 at 2:38 AM, Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
>
>> Pawel,
>>
>> Thanks, this looks interesting.
>>
>> 1) why are you using such an old driver?
>>
>
> Only for the "If it ain't broke, don't touch it" principle :) It's a part
> of a large J2EE application. Will probably update it along with other
> middleware at some point.
>
>
>> 2) what are you referring to with the comment about it not being async?
>>
>
> My original question was about "async notifications". Technically async in
> this case would mean calling back on a separate thread. This fix calls back
> on the same thread. So it needs to be realized that any work inside that
> call back will affect the execution of the statement.
>
>
>>
>> Dave Cramer
>>
>> dave.cramer(at)credativ(dot)ca
>> http://www.credativ.ca
>>
>> On 27 January 2015 at 17:33, Pawel Veselov <pawel(dot)veselov(at)gmail(dot)com>
>> wrote:
>>
>>>
>>> [skipped]
>>>
>>>
>>>> I've put together this patch (over 9.1-902, which is just what I
>>>> currently use), if anybody's interested: http://pastebin.com/KftdtdNq
>>>> ,but:
>>>> - it uses JDK6 stuff
>>>> - has effect of copying all statements/resultset warnings into
>>>> connection warnings
>>>>
>>>
>>> And one other thing. That's not asynchronous, it simply provides
>>> callbacks into the caller's app to allow to process notifications as they
>>> are received.
>>>
>>> [skipped]
>>>
>>
>>
> --
> With best of best regards
> Pawel S. Veselov
>