From: | Pawel Veselov <pawel(dot)veselov(at)gmail(dot)com> |
---|---|
To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: How can this abstract method error happen? |
Date: | 2014-01-14 01:05:48 |
Message-ID: | CAMnJ+Bdgg=jNu7YvEPVjJJzGMaRmqwPWhKR_gt86MAoR2suAEQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Mon, Jan 13, 2014 at 4:29 PM, Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
> Is there anything else in the exception chain ?
>
Nope, but I don't see how there would be.
>
> On Mon, Jan 13, 2014 at 6:26 PM, Pawel Veselov <pawel(dot)veselov(at)gmail(dot)com>wrote:
>
>> Hi.
>>
>> I'm getting an abstract method error problem with Postgres JDBC (top of
>> exception trace:http://pastebin.com/xsDKSdiE). There isn't a stable way
>> to reproduce this that I found. The driver is 9.1-902.
>>
>> I don't quite understand how this can even happen. Looks like all the all
>> statement object are created by the connection object, and all connection
>> objects are created by the Driver. Driver always creates connection version
>> 4, and that connection always creates statements version 4, so it should
>> always implement isClosed(). I never ever used any earlier drivers (so I
>> don't think there is C/P mess up, but I grepped my class path too).
>>
>> Can anything else ever create a connection object, which can be of
>> earlier version?
>>
>>
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2014-01-14 11:26:33 | Re: How can this abstract method error happen? |
Previous Message | Dave Cramer | 2014-01-14 00:29:28 | Re: How can this abstract method error happen? |