PreparedStatement.setDate(int, Date) problem in WHERE clause

Question

Hello all,
First and foremost, thanks for the help. It is really appreciated.
I am having the toughest time tracking down a problem with how I am handling date setting with my PreparedStatement. The kicker is that I am only having problems with the where clause date sets.
The date is pulled out of the database, put into a string, modified, put back into a date, and then used to query via SQL.
Data selected this way:
"SELECT * FROM table_name"
Data updated this way:
"UPDATE table_name SET name = ? WHERE pk_id = ? AND pk_date = ?"
The java.sql.Date object I use to PreparedStatement.setDate(int, Date) is exact to seconds. It works great if it is not in the where clause (eg Inserts work, Updates work without where clause) which leads me to believe there is truncation of data somewhere between setDate(int, Date) and the native SQL in Oracle 9i.
Is that a correct assumption? How do I solve this?
Thanks,
John

Answer 1

My assumption was correct. If a java.sql.DATE is pulled from a Oracle 9i database it may have more data in it than is allowed for in java.sql.Date. java.sql.Timestamp, on the other hand, does retain all data in the field.
The correct code looks something like this
prepStmt.setTimestamp(Timestamp.valueOf(timeString));
cheers,
John