Skip site navigation (1) Skip section navigation (2)

Re: Bug? report : PreparedStatement.setObject(java.util.Date) don't work

From: 雨森郷太郎 <gotaroamenomori(at)gmail(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Bug? report : PreparedStatement.setObject(java.util.Date) don't work
Date: 2007-11-10 05:24:23
Message-ID: 3a69fa320711092124hf008c72p471af0d968729c11@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
Thank you for reply.

>Try using java.sql.Date instead of java.util.Date, there should be a
>mapping for that.

It should work, I agree.

However, Is there reason to refrain from supporting java.util.Date ?

Originaly, I developed my Java Web application on postgres version7.4.
On the environment, java.util.Date to java.sql.Types#DATE mapping
worked well via JDBC ver7.4, like
http://jdbc.postgresql.org/download/pg74.216.jdbc3.jar
I can't see sources of the version, but I guess it has mapping for
java.util.Date.

Recently, I upgraded my Postgres DBMS to ver.8.2, and replaced
JDBC to "8.2 Build 506" then faced problem.

Now, I'm using source compiled Dirver with modification I reported.
I hope java.util.Date mapping to be original specification.

How's this?

Gotaro AMENOMORi

In response to

Responses

pgsql-jdbc by date

Next:From: Oliver JowettDate: 2007-11-10 09:28:56
Subject: Re: Bug? report : PreparedStatement.setObject(java.util.Date) don't work
Previous:From: Oliver JowettDate: 2007-11-10 01:27:15
Subject: Re: Bug? report : PreparedStatement.setObject(java.util.Date) don't work

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group