[
https://issues.apache.org/jira/browse/DERBY-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15335175#comment-15335175
]
Yair Lenga edited comment on DERBY-4555 at 6/17/16 1:38 AM:
------------------------------------------------------------
I'm submitted the original request, assuming it will be a minor effort to get
the requested change in. It looks to me that the implementation path of
extending the existing procs into var-args make the implementation much harder.
Given this information, will it be possible to register a new proc(e.g.)
"SYSCS_IMPORT_BULK" that will have the additional functionality, implemented
with required parameter (skip, integer) ?
I think that most users (myself included) will find the it more important to
improve the support for CSV with headers including reference to column names,
as specified in the request - and will not care if the proc name is the same.
Given the effort (and risk), it probably make sens only to extend the (more
flexible) IMPORT_DATA, and leave the IMPORT_TABLE unmodified.
With all those changes, I'm worried that something will break in the current
proc, which perform critical role
was (Author: yairlenga):
I'm submitted the original request, assuming it will be a minor effort to get
the requested change in. It looks to me that the implementation path of
extending the existing procs into var-args make the implementation much harder.
Given this information, will it be possible to register a new proc
"SYSCS_IMPORT_BULK" that will have the additional functionality, implemented
withrequired parameter (skip, integer) ? I think that most users (myself
included) will find the it more important to improve the (semi) standard excel
headers, including reference to column names, as specified in the request - and
will not care if the proc name is the same. Given the effort, it probably make
sens only to extend the (more flexible) IMPORT_DATA, and leave the IMPORT_TABLE
unmodified.
With all those changes, I'm worried that something will break in the current
proc, which perform critical role
> Expand SYSCS_IMPORT_TABLE to accept CSV file with header lines
> --------------------------------------------------------------
>
> Key: DERBY-4555
> URL: https://issues.apache.org/jira/browse/DERBY-4555
> Project: Derby
> Issue Type: Improvement
> Components: Miscellaneous
> Reporter: Yair Lenga
> Assignee: Danoja Dias
> Attachments: NoVarargs.diff, Varargs.diff, gotException.diff,
> hardCoded.diff, latest.diff, noHeaderLines.csv, petlist.csv, petlist.csv,
> petlist.csv, repro.java, repro.java, skipHeaders.diff
>
>
> The SYSCS_IMPORT_TABLE (and SYSCS_IMPORT_DATA) function allow import of data
> from external resources. In general, they can process CSV files that created
> with various tools - with one exception: the header line.
> While there is no accepted standard, most tools will include a header line in
> the CSV file with column names. This convention is supported in Excel and
> many other tools.
> My Request: extend the SYSCS_IMPORT_TABLe and SYSCS_IMPORT_DATA (and other
> related procedures) to include an extra indicator for the number of header
> lines to be ignored.
> As an extra bonus it will be help is the SYSCS_IMPORT_DATA will accept column
> names (instead of column indexes) in the 'COLUMNINDEXES' arguments. E.g., it
> should be possible to indicate COLUMNINDEXES of '1,3,sales,5,'. This feature
> will make it significantly easier to handle cases where the external input
> files is extended to include additional columns.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
