[
https://issues.apache.org/jira/browse/DERBY-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-4555:
-----------------------------------
Attachment: repro.java
noHeaderLines.csv
Attached is the repro.java that I am using, and the noHeaderLines.csv
file that I used. I also added a 'println' to
SystemProcedures.SYSCS_IMPORT_TABLE
so I could see that I was running the code I thought I was running.
When I run with that configuration, with Varargs.diff applied
and built, I see:
[bpendleton@Fedora22 DERBY-4555]$ rm -rf derbyDB/ ; java -cp
/home/bpendleton/derby/trunk/classes:. repro
repro starting in embedded mode
Created database derbyDB
Created table A
SYSCS_IMPORT_TABLE: replace[0]=0
Table is imported
Rover, Dog,4
Spot, cat,2
Squawky, Parrot,37
repro finished
> 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
>
>
> 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)
