[
https://issues.apache.org/jira/browse/DERBY-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15349025#comment-15349025
]
Bryan Pendleton commented on DERBY-6892:
----------------------------------------
It's not obvious to me why the order of arguments change matters, but I think
it's a very good theory. The Derby engine is quite sophisticated in this area;
there are places where it actually stores things like system procedures and
stored prepared statements as Java bytecode sequences, which would then be
"pre-compiled" to a certain order of arguments, and would not automatically
adapt to a different argument ordering.
Do you think it might be possible to re-arrange your changes so that the order
of the 'replace' and 'lobsInExtFile' arguments are *not* swapped?
If you can see a way to do that, it would be very interesting to know if that
makes the test pass.
> Create new SYSCS_IMPORT_TABLE_BULK procedure
> --------------------------------------------
>
> Key: DERBY-6892
> URL: https://issues.apache.org/jira/browse/DERBY-6892
> Project: Derby
> Issue Type: Sub-task
> Components: SQL
> Reporter: Bryan Pendleton
> Assignee: Danoja Dias
> Priority: Minor
> Attachments: addNewSystemProcedure.diff
>
>
> As a sub-task of DERBY-4555, we propose to create a new
> system procedure, SYSCS_IMPORT_TABLE_BULK, which supports
> all the functionality of SYSCS_IMPORT_TABLE, but additionally supports
> skipping multi-line column headers in the input file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
