[ https://issues.apache.org/jira/browse/DERBY-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lily Wei updated DERBY-4789:
----------------------------
Attachment: DERBY-4789-AddMoreTests3.diff
I forgot to mention I did not find any more issue. Thank to great work of bulk insert. And, I was attaching my version of TableFunctionTest.java instead of the .diff that only include the tests on top of DERBY-4789-QuestionTest2.diff. Sorry for the confusion. Thanks.
> Always apply the bulk-insert optimization when inserting from a table function.
> -------------------------------------------------------------------------------
>
> Key: DERBY-4789
> URL: https://issues.apache.org/jira/browse/DERBY-4789
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Reporter: Rick Hillegas
> Attachments: derby-4789-01-ab-alwaysForTableFunctions.diff, DERBY-4789-AddMoreTests3.diff, DERBY-4789-QuestionTest.diff, DERBY-4789-QuestionTest2.diff, TableFunctionTest.java
>
>
> Inserting from a table function is a lot like importing from a file:
> 1) Derby has limited visibility into the size of the external data source.
> 2) The user is often trying to import a large data set.
> The import procedures assume that Derby should always apply the bulk-insert optimization when importing from a file. The same assumption seems reasonable whenever a table function appears in the source stream of an INSERT.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.