db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-4555) Expand SYSCS_IMPORT_TABLE to accept CSV file with header lines
Date Wed, 15 Jun 2016 13:47:09 GMT

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

Bryan Pendleton commented on DERBY-4555:
----------------------------------------

I think the problem here is that SYSCS_IMPORT_TABLE is a system procedure,
not a schema descriptor.

I am not sure that the DataDictionary class currently has an API method
that allows clients to ask it to drop a system procedure.

We may need to do a little bit more investigation here, to think
about exactly what we need to provide.

Derby does provide a DROP PROCEDURE statement, for dropping user-created
Java stored procedures. We could try tracing through that code, to see
how it accomplishes that task, but I am not sure if dropping a system
procedure is precisely the same as dropping a user's stored procedure.

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

Mime
View raw message