Re: issues with SQL size st.execute(SQL) in 8.3.3

HI All,
Can we call a psotgres procedure through JAVA Csllable statemnt
Thanks and Regards,
Ramasubramanian.G|Software Engineer - Delivery
E-mail:ramasubramanian(dot)g(at)renaissance-it(dot)com | Extn: 1607
Sobha Renaissance Information Technology (P) Ltd.
An SEI-CMM, P-CMM & SSE-CMM Level 5 Company
BS ISO/IEC 27001:2005 & ISO 9001:2000 Certified

A Top 50 Fast Growing Technology Company (Deloitte, 2006 & 2007) |
A Six Sigma Practice Company
Phone: + 91 80 41951999 |
Fax: + 91 80 41523300 A Top 50 Fast Growing Technology Company (Deloitte,
2006 & 2007) |
A Six Sigma Practice Company
Phone: + 91 80 41951999 |
Fax: + 91 80 41523300

URL: www.renaissance-it.com |
Video Conference: + 91 80 41252222
?
----- Original Message -----
From: "Achilleas Mantzios" <achill(at)matrix(dot)gatewaynet(dot)com>
To: <pgsql-jdbc(at)postgresql(dot)org>
Cc: "Kris Jurka" <books(at)ejurka(dot)com>
Sent: Saturday, October 18, 2008 11:03 AM
Subject: Re: [JDBC] issues with SQL size st.execute(SQL) in 8.3.3

Στις 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