From: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
---|---|
To: | Postgres JDBC <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | backwards compatibility problem |
Date: | 2006-05-10 16:27:46 |
Message-ID: | 1147278466.14093.341.camel@coppola.muc.ecircle.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hi all,
I was trying to upgrade the postgres JDBC driver I was using due to the
fix for supporting high-unicode characters.
I was using before the file:
postgresql-8.1dev-400.jdbc3.jar
and upgraded to:
postgresql-8.1-405.jdbc3.jar
The new one fixes indeed the high-unicode character support, but it
breaks other code we have...
Specifically, with the former driver the following query would work:
select ? - '1 day'::interval
where the parameter is set to a timestamp value (either via setTimestamp
or setObject without specifying the type, the result is the same).
With the new driver the same code results in:
ERROR: invalid input syntax for type interval: "2006-05-10
18:15:47.679000 +0200"
Casting the ? sign to timestamp in the query works here (tested), but I
wonder why this was working in the older driver and stopped working with
the newer. AFAIK the protocol did not change and strict typing was
required already with the old driver, so how come that got it right and
the new one does not ?
Thanks,
Csaba.
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Lewis | 2006-05-10 16:33:11 | Re: Query length restriction in v3 protocol? |
Previous Message | Dan Armbrust | 2006-05-10 14:43:35 | Re: Problem dropping a table |