commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CSV-82) CSVRecord inconsistent behaviour when header mapping is not found
Date Mon, 26 Mar 2012 13:16:28 GMT

    [ https://issues.apache.org/jira/browse/CSV-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238362#comment-13238362
] 

Sebb commented on CSV-82:
-------------------------

bq. In case 2 a null value is returned, because some column may be optional.

I don't understand this concept of optional columns.
Surely any CSV header line needs to provide names for all the columns?
Otherwise, what's the point of the header line?
                
> CSVRecord inconsistent behaviour when header mapping is not found
> -----------------------------------------------------------------
>
>                 Key: CSV-82
>                 URL: https://issues.apache.org/jira/browse/CSV-82
>             Project: Commons CSV
>          Issue Type: Bug
>            Reporter: Sebb
>
> The CSVRecord#get(String) method has inconsistent behaviour.
> If no header mapping was provided, then it throws IllegalStateException.
> If the header name is not found, null is returned.
> Apart from being inconsistent, it might be useful in the future to be able to return
null as a column value (as distinct from the empty string).
> It should throw IllegalArgumentException for a missing header name, instead of returning
null.

--
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