[
https://issues.apache.org/jira/browse/DERBY-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369919#comment-15369919
]
Bryan Pendleton edited comment on DERBY-6894 at 7/10/16 7:48 PM:
-----------------------------------------------------------------
I think the new symbolic error name in SQLState.java might be better named:
String LANG_INVALID_INPUT_COLUMN_NAME =
"42XAU";
since LANG_INVALID_COLUMN_NAME sounds rather like it might
refer to a column in the *table*, not a column in the *input file*
was (Author: bryanpendleton):
I think the new symbolic error name in SQLState.java might be better named:
String LANG_INVALID_INPUT_COLUMN_NAME =
"42XAU";
since LANG_INVALID_COLUMN_NAME sounds rather like it might
refer to a column in the **table**, not a column in the **input file**
> Enhance COLUMNINDEXES parsing for SYSCS_IMPORT_DATA_BULK to recognize columns
> by name
> -------------------------------------------------------------------------------------
>
> Key: DERBY-6894
> URL: https://issues.apache.org/jira/browse/DERBY-6894
> Project: Derby
> Issue Type: Sub-task
> Components: SQL
> Reporter: Bryan Pendleton
> Assignee: Danoja Dias
> Priority: Minor
> Attachments: Derby-6894.diff, NewDerby6894.diff, NewDerby6894_2.diff,
> noHeaderLines.csv, petlist.csv, repro.java, repro.java
>
>
> To ease maintainability and legibility of client programs, it would be
> nice if callers of SYSCS_IMPORT_DATA_BULK (and possibly also
> SYSCS_IMPORT_DATA) could refer to columns in the COLUMNINDEXES
> argument by column *NAME*, as well as by index *NUMBER*.
> So, for example, a valid COLUMNINDEXES specification might be:
> '1,3,LastName,FirstName,7'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
