Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-2203

update with subquery route to slave

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2.17
    • Component/s: qc_sqlite
    • Labels:
      None
    • Environment:
      2.2.12

      Description

      Following query parsed as QUERY_OP_SELECT

      UPDATE test1 AS log_funnel
                       INNER JOIN (SELECT inner_funnel.idvisit, min(step_position) as minstep, max(step_position) as maxstep 
                              FROM test1 inner_funnel
                              LEFT JOIN pwk_log_visit log_visit on inner_funnel.idvisit = log_visit.idvisit
                              WHERE inner_funnel.idfunnel = '10' 
                                    AND log_visit.idsite = '8' 
                                    AND log_visit.visit_last_action_time >= '2018-12-02 16:00:00'
                                    AND log_visit.visit_last_action_time <= '2018-12-03 15:59:59'
                              GROUP BY inner_funnel.idvisit) lf
                        SET log_funnel.min_step = lf.minstep, log_funnel.max_step = lf.maxstep 
                        WHERE log_funnel.idvisit = lf.idvisit
                              AND log_funnel.idfunnel = '10' 
                              AND log_funnel.min_step != lf.minstep
                              AND log_funnel.max_step != lf.maxstep
      

        Attachments

          Activity

            People

            Assignee:
            johan.wikman Johan Wikman
            Reporter:
            dapeng dapeng huang
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.