[SQOOP-456] Generated Java class does not distinguish date and timestamp in Oracle DB

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Component/s: codegen
• Assignee: Unassigned
• Reporter: Cheolsoo Park
• Created: 07/Mar/12 08:01
• Updated: 02/Jul/13 17:50
• Resolved: 15/Oct/12 16:22

Description

In genereated Java class, both date and timestamp are considered as timestamps. For examples, the following getter method is generated for a date column:

 
public void readFields(ResultSet __dbResults) throws SQLException {
  this.__cur_result_set = __dbResults;
  this.DATA_COL0 = JdbcWritableBridge.readTimestamp(1, __dbResults);
}

This happens because both date and timestamp is labeled as Types.TIMESTAMP by ConnManager. The fix seems straightforward. In ClassWriter, the new method getColTypeNamesForTable introduced by Bilung at SQOOP-352 should replace getColTypes().