Re: Problems with protocol V3 after migration to latest driver

Ah, except that thing with "at time zone":

select now() at time zone ('-02:00'::interval);
works OK in psql console;

but with JDBC
select now() at time zone (?::interval)
with setString(1, '-02:00')
gives me
java.sql.SQLException: ERROR: cannot cast type character varying to interval
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1240)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1043)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:138)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:347)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:294)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:209)

-----Original Message-----
From: Alexey Yudichev
Sent: Tuesday, October 26, 2004 1:00 PM
To: Kris Jurka
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [JDBC] Problems with protocol V3 after migration to latest driver

Works perfectly now, thanks.
I have also run the full test suite of my largest project with these new drivers and V3 and 7.4.5 server and it showed no problems. So the planner problem is the only one that remains with V3, is there a way to figure it out or 8.0 server is the only solution? Is V3 protocol support in 7.4 server considered experimental or is it an issue of JDBC drivers?

-----Original Message-----
From: Kris Jurka [mailto:books(at)ejurka(dot)com]
Sent: Tuesday, October 26, 2004 10:41 AM
To: Alexey Yudichev
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [JDBC] Problems with protocol V3 after migration to latest driver

On Tue, 26 Oct 2004, Alexey Yudichev wrote:

> No, it is still there with pgdev.307ay2.jdbc3.jar:
>
> java.sql.SQLException: ERROR: large object 36405664 does not exist

OK, I've tracked this one down. Some bit shifting code had a typo in it,
that only affected sufficiently large oid values. This is why you only
saw the error on one machine.

Newly updated jar files available again from
http://www.ejurka.com/pgsql/jars/alexey/

Kris Jurka

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org