On Tue, 20 Mar 2001, Barry Lind wrote:
> Actually it was the changes in version 1.21 on 2/13 that broke this.
> The cvs log for that change includes the following comment:
> - Removed need for SimpleDateFormat in ResultSet.getDate() improving
> performance.
Yes, of course. My mistake.
> My guess is the the code as written would work correctly for a 'date'
> column, but doesn't work for a 'timestamp' column. Is there a reason
> you are not using getTimestamp() to get the value of the timestamp column?
The reason is that the code contains getDate() because it used to work and
we need to print it in date format. The Java SDK1.3 api description does
just say, that it
gets the value of the designated column in the current row
of this ResultSet object as a java.sql.Date object in the Java programming language.
It does not imply that the underlying column cannot be of Timestamp type,
since e.g. getString() works fine on numeric etc.
I do not know how many people have similar issues, but less performance
for more robustness would be my call in this case (i.e. rollback to
earlier version).
But if other people do not experience those problems I'll look forward to
the modifications that Peter T Mount mentioned:
("One of the first things I'm doing once 7.1 is out is add some sanity
checking so that the get/set methods on Date, Timestamp, integer, double
etc so that getDate() on a Timestamp would work, but also
getTimestamp() on a Date column.")
and have a workaround for the mean time.
Regards,
Juhan Ernits
