JDBC ResultSet getDate losing precision

Question

I am losing precision in my ResultSet.getDate(x) calls. Basically:

rs = ps.executeQuery();
rs.getDate("MODIFIED");

is returning dates truncated to the day where MODIFIED is an Oracle TIMESTAMP field of default precision. I think there may be some JDBC tweak I'm missing; usually TIMESTAMP is compatible with DATE, but I'm hoping I don't have to redefine the entire table.

score 63 · Accepted Answer · edited Jul 17 '14 at 11:51

63

ResultSet.getDate() returns a java.sql.Date, not a java.util.Date. It is defined to be a timeless date. If you want a timestamp, use ResultSet.getTimestamp()!

edited Jul 17 '14 at 11:51

Ypsilon

122
1
9

answered Jul 16 '10 at 15:50

Affe

47,174
11
83
83

4

Note to self - rtfm. I thought this was working in other places. – orbfish Jul 19 '10 at 13:43
2

"java.sql.Date is defined to be a timeless date". That statement has saved my life. Thank you! – Bitcoin Cash - ADA enthusiast Aug 28 '12 at 04:37

dpatchery · Answer 2 · 2010-07-16T16:02:47.557

4

You should use java.sql.Timestamp instead of java.sql.Date. You can use it as a java.util.Date object afterward if necessary.

rs = ps.executeQuery();
Timestamp timestamp = rs.getTimestamp("MODIFIED");

Hope this helps.

edited Jul 16 '10 at 16:02

answered Jul 16 '10 at 15:50

dpatchery

508
5
19

2

Constructing `new Date` is unnecessary since `Timestamp extends Date`. – BalusC Jul 16 '10 at 15:56

score 0 · Answer 3 · answered Aug 10 '12 at 13:13

0

Using Timestap is the correct way. Please take not that with Timestamp you will not be able to set the columns to nullable if you were to use Liquibase.

A problem I came across as well.

answered Aug 10 '12 at 13:13

Ali

1

JDBC ResultSet getDate losing precision

3 Answers3

Linked

Related