[ https://issues.apache.org/jira/browse/DERBY-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Danoja Dias updated DERBY-4555: ------------------------------- Attachment: addNewSystemProcedure.diff I added new system procedure with the new argument. When I run repro.java with the new procedure, I got an exception like this. java.sql.SQLSyntaxErrorException: 'SYSCS_UTIL.SYSCS_IMPORT_TABLE_SKIP_HEADER_LINES' is not recognized as a function or procedure. Diff is attached as addNewSystemProcedure.diff Is there any thing I missed? > 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, > addNewSystemProcedure.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)