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

FULL OUTER JOIN Allowed JOIN Orders

    XMLWordPrintable

Details

    • Task
    • Status: In Progress (View Workflow)
    • Major
    • Resolution: Unresolved
    • 12.3
    • Optimizer
    • None
    • Q4/2025 Server Development

    Description

      Taking from MDEV-36813:

      If the query has 

        t1 full outer join t2 on on_cond

      then t1 and t2 may only be together in the join order.
      It can be ... t1 t2 ... or ... t2 t1...

      Need to modify check_interleaving_with_nj() and JOIN::get_allowed_nj_tables()
      to enforce that.

      (Just have each table remember its full-outer-join peer, if any. If the last table
      in the join order has a peer, only allow that peer as the next table)

      Attachments

        Issue Links

          split from

          New Feature - A new feature of the product, which has yet to be developed. MDEV-36813 DRAFT: FULL OUTER JOIN for single table

          • Major - Major loss of function.
          • In Progress

          Activity

            People

              Gosselin Dave Gosselin
              Gosselin Dave Gosselin
              Dave Gosselin Dave Gosselin
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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