sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cheolsoo Park (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SQOOP-456) Generated Java class does not distinguish date and timestamp in Oracle DB
Date Wed, 07 Mar 2012 08:01:59 GMT
Generated Java class does not distinguish date and timestamp in Oracle DB 
--------------------------------------------------------------------------

                 Key: SQOOP-456
                 URL: https://issues.apache.org/jira/browse/SQOOP-456
             Project: Sqoop
          Issue Type: Bug
          Components: codegen
            Reporter: Cheolsoo Park
            Assignee: Cheolsoo Park


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

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

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(). 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message