Re: issues with SQL size st.execute(SQL) in 8.3.3 - Mailing list pgsql-jdbc

From Achilleas Mantzios
Subject Re: issues with SQL size st.execute(SQL) in 8.3.3
Date
Msg-id 200810180833.40691.achill@matrix.gatewaynet.com
Whole thread Raw
In response to Re: issues with SQL size st.execute(SQL) in 8.3.3  (Kris Jurka <books@ejurka.com>)
Responses Re: issues with SQL size st.execute(SQL) in 8.3.3  (Kris Jurka <books@ejurka.com>)
List pgsql-jdbc
Στις Friday 17 October 2008 20:34:57 ο/η Kris Jurka έγραψε:
>
> On Fri, 17 Oct 2008, Achilleas Mantzios wrote:
>
> > As a quick and dirty workaround, i tried setting protocolVersion=2 and
> > it worked. Can you see any potential side effects about it as a
> > temporary solution to the problem?
>
> It all depends on whether you are relying on any V3 features in other
> places.  I have a fix for the issue (attached).  I'm still testing it and
> will hopefully apply it this weekend.

Regarding V2, its just a simple program like the one i showed,
can you point some cases which would explicitly rely on V3 features ?
Which JDBC method calls would be affected by the enforcement of V2?
Can the rest of the backends (other than the one serving the v2 client) be
affected in any way by this?
>
> Kris Jurka



--
Achilleas Mantzios

pgsql-jdbc by date:

Previous
From: Kris Jurka
Date:
Subject: Re: issues with SQL size st.execute(SQL) in 8.3.3
Next
From: "Ramasubramanian"
Date:
Subject: Re: issues with SQL size st.execute(SQL) in 8.3.3