From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | alvin(dot)yk(at)gmail(dot)com |
Cc: | pgsql-jdbc(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: 8.0.1 performance question. |
Date: | 2005-04-04 17:05:17 |
Message-ID: | Pine.BSO.4.56.0504041202050.2383@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc pgsql-performance |
On Tue, 5 Apr 2005 alvin(dot)yk(at)gmail(dot)com wrote:
> Thank you for the quick response. To help me debug what's happening,
> can you tell me what's the difference between the 7.4 and 8.0 jdbc
> drivers in this regard? Is this something that is newly introduced in
> 8.0? Or is this something that has always been happening?
>
8.0 is the first driver version to take advantage of the V3 protocol's
ability to return the base tables and columns of a ResultSet.
Previously isNullable was hardcoded to always return
columnNullableUnknown and isAutoIncrement always returned false.
I guess the question is why are you calling these methods if they didn't
work previously?
Kris Jurka
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2005-04-04 17:09:18 | Re: JDBC and transactions |
Previous Message | alvin.yk | 2005-04-04 16:44:26 | Re: 8.0.1 performance question. |
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Turner | 2005-04-04 19:12:20 | Re: How to improve db performance with $7K? |
Previous Message | Christopher Petrilli | 2005-04-04 16:51:17 | Re: Sustained inserts per sec ... ? |