Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-4789

Always apply the bulk-insert optimization when inserting from a table function.

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 10.6.2.4, 10.7.1.1
    • SQL
    • None
    • Performance

    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.

      Attachments

        1. derby-4789-01-ab-alwaysForTableFunctions.diff
          12 kB
          Richard N. Hillegas
        2. DERBY-4789-QuestionTest.diff
          1.0 kB
          Lily Wei
        3. DERBY-4789-QuestionTest2.diff
          1 kB
          Lily Wei
        4. TableFunctionTest.java
          88 kB
          Lily Wei
        5. DERBY-4789-AddMoreTests3.diff
          6 kB
          Lily Wei

        Issue Links

          Activity

            People

              rhillegas Richard N. Hillegas
              rhillegas Richard N. Hillegas
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: