You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2012/09/20 20:56:07 UTC
[jira] [Resolved] (DERBY-4789) Always apply the bulk-insert
optimization when inserting from a table function.
[ https://issues.apache.org/jira/browse/DERBY-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mamta A. Satoor resolved DERBY-4789.
------------------------------------
Resolution: Fixed
> 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
> Assignee: Rick Hillegas
> Fix For: 10.6.2.3, 10.7.1.1
>
> Attachments: derby-4789-01-ab-alwaysForTableFunctions.diff, DERBY-4789-AddMoreTests3.diff, DERBY-4789-QuestionTest2.diff, DERBY-4789-QuestionTest.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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira