| From: | Bill Bunting <bunting(at)incentivemeetings(dot)com> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Cc: | cameron Tabor <ctabor(at)incentivemeetings(dot)com> |
| Subject: | ResultSet.getTimestamp() Exception (UPDATE) |
| Date: | 2000-12-20 02:52:28 |
| Message-ID: | 5.0.0.25.2.20001219214306.00a3f510@pop.incentivemeetings.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
I downloaded the postgresql-7.0.3.tar.gz source and compiled the JDBC
driver using make jdbc2, installed the new JAR file and it works
now. There may be a problem in the RPM or something. Sorry that I can not
be more specific. Thank you.
Previously, I wrote:
------------------------
Version: Postgresql 7.0.3-2 (RPM for RedHat6.2)
JDBC Version: 7.0.3-2 (RPM for RedHat6.2)
Java Version: Sun build 1.3.0
Calls to ResultSet.getTimestamp(...) throw an exception and report the
following error:
"Bad Timestamp Format at 19 in 2000-12-18 12:31:15.77-05"
To reproduce:
1. Create a table using the TIMESTAMP SQL type.
2. Insert a row with a timestamp (using psql)
3. Use JDBC getTimestamp()
For use, this bug is severe since it prevents us from using the timestamps
in our EJB entity beans.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2000-12-20 03:11:31 | Backend dies when overloading + operator for bool |
| Previous Message | Peter Eisentraut | 2000-12-19 22:51:35 | Re: Re: Table name scope (was Re: [BUGS] Outer joins aren't working with views) |