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

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

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.1(EOL)
    • 10.1.6
    • Optimizer
    • 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

          Ascending order - Click to sort in descending order
          bar Alexander Barkov created issue -
          bar Alexander Barkov made changes -
          Field Original Value New Value
          Fix Version/s 10.1 [ 16100 ]
          bar Alexander Barkov made changes -
          Assignee Alexander Barkov [ bar ]
          bar Alexander Barkov made changes -
          Fix Version/s 10.1.6 [ 19401 ]
          Fix Version/s 10.1 [ 16100 ]
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Closed [ 6 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 70034 ] MariaDB v4 [ 149279 ]

          People

            bar Alexander Barkov
            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.