[DERBY-4789] Always apply the bulk-insert optimization when inserting from a table function.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 10.6.2.4, 10.7.1.1
• Component/s: SQL
• Bug behavior facts: Performance
• Assignee: Richard N. Hillegas
• Reporter: Richard N. Hillegas
• Created: 01/Sep/10 13:26
• Updated: 14/Jun/13 17:33
• Resolved: 20/Sep/12 18:54

Description

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.

Issue Links

• is part of: DERBY-4788 Automatically apply the bulk-insert optimization when the size of the source stream warrants it.