[
https://issues.apache.org/jira/browse/DERBY-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906110#action_12906110
]
Lily Wei commented on DERBY-4789:
---------------------------------
Question: I am not totally know whether this should trigger a bulk insert or
not.
It is a self join that wrap a table function in a view.
When test with bulkInsertTable empty, I got bulk insert by having different
conglomeratenumber.
However, when test by adding the following code:
vetBulkInsert
(
conn,
"insert into bulkInsertTable select * from bulkInsertView b where
1 = (select count(*) from bulkInsertView bc where b.column0 > bc.column0)",
true
);
It did not trigger bulk insert.
> 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
>
>
> 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.
