Hello,
I am working with JDBC and MySQL. I have a date column that I need included in my result set. Unfortunately, I cannot find a class in Java to retrieve the date. The SQL Date class is deprecated. How do you get Date objects from a result set?
+3
A:
I don't think the java.sql.Date class itself it deprecated, only one of its constructors. You should be safe to continue using it.
Adam Paynter
2009-05-20 12:37:41
+14
A:
You use java.sql.Date. A constructor and some methods are deprecated. The class isn't. Confused by this versus, say, java.util.Date or java.util.Calendar? Look at Making Sense of Java's Dates.
There are three JDBC date/time types:
- DATE: granularity of days, use java.sql.Date;
- TIMESTAMP: date and time, use java.sql.Timestamp;
- TIME, just the time with no date, use java.sql.Time.
The confusion probably arises from the fact that java.sql.Date extends java.util.Date and thus inherits its deprecated methods.
Just use the right type for the type of your column.
cletus
2009-05-20 12:38:28
short and to the point and very helpful. +1
Jason S
2009-05-20 12:46:29
The problem is that the only constructor that remains is the one to create a date passing in millis. Also, all of its set and get methods that don't use millis are deprecated. Unless SQL returns the date in millis this seems kind of silly.
Ryan H
2009-05-20 12:55:21
Read the javadoc more closely, java.sql.Date conforms to the DATE JDBC type and the fields smaller than day are set to zero. The type is for use when you have a field that is day/month/year only and not, say, TIMESTAMP or TIME. What are you trying to do exactly?
cletus
2009-05-20 12:59:11
Oh that makes more sense thanks
Ryan H
2009-05-20 13:17:36
and don't forget that java.sql.Date is a subclass of java.util.Date (some more methods)
Carlos Heuberger
2009-05-20 18:26:59
+1
A:
You can safely use the java.sql.Date class to map your MySQL DATE type. The java.sql.Date class extends the java.util.Date class, so you can use this object to do all types of date calculations.
Fortega
2009-05-20 12:46:33
+1
A:
Old post, but anyways:
I had problems with the granularity of java.util.Date and switched to java.util.Timestamp. I also experienced limited granularity with Timestamp type (up to seconds).
The columns in the database are declared as Date and to get the additional time part, I retrieved it as Timestamp. Problem is it truncates the value to seconds.
I investigated the Oracle default definition for timestamp which allows for 6 fractional digits.
I guess the Date part in the oracle definition limits the timestamp part in Java...
Cheers, Grazina
Grazina
2009-12-23 17:47:14
That is exactly as per the JDBC contract. If you want to store a date (day, month, year), use `java.sql.Date`. If you want to store a time (hour, minute, second), use `java.sql.Time`. If you want to store a timestamp (day, month, year, hour, minute, second, also known as datetime), use `java.sql.Timestamp`. Depending on the DB and JDBC driver used you also have milliseconds in the `Timestamp`.
BalusC
2009-12-24 09:33:05