Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-8330

Get rid of Item_func::select_optimize() and Item_func::optimize_type

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.1
    • Fix Version/s: 10.1.6
    • Component/s: Optimizer
    • Labels:
      None

      Description

      After a set of patches made under terms MDEV-7950, Item_func::select_optimize() and Item_func::optimize_type have now a very little sense.

      select_optimize() is now used only in Item_func::get_mm_tree().

      We just need to split Item_func::get_mm_tree() into:

      • a non-optimized default implementation for Item_func::get_mm_tree(),
      • an optimized implemetation for Item_bool_rowready_func2::get_mm_tree()
      • an optionally optimized implementation in Item_func_like::get_mm_tree().

        Attachments

          Activity

            People

            Assignee:
            bar Alexander Barkov
            Reporter:
            bar Alexander Barkov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.