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

cte_recursive test fails with ps-protocol

    XMLWordPrintable

    Details

      Description

      perl ./mtr main.cte_recursive --ps-protocol
      

      main.cte_recursive                       [ fail ]
              Test ended at 2016-09-24 17:14:40
       
      CURRENT_TEST: main.cte_recursive
      mysqltest: At line 1165: query 'create table my_ancestors
      with recursive
      ancestor_ids (id)
      as
      (
      select father from folks where name = 'Me'
        union
      select mother from folks where name = 'Me'
        union
      select father from folks, ancestor_ids a  where folks.id = a.id
      union
      select mother from folks, ancestor_ids a  where folks.id = a.id
      )
      select p.* from folks as p, ancestor_ids as a where p.id = a.id' failed: 1146: Table 'test.ancestor_ids' doesn't exist
       
      The result from queries just before the failure was:
      < snip >
                }
              }
            }
          }
        }
      }
      create table my_ancestors
      with recursive
      ancestor_ids (id)
      as
      (
      select father from folks where name = 'Me'
        union
      select mother from folks where name = 'Me'
        union
      select father from folks, ancestor_ids a  where folks.id = a.id
      union
      select mother from folks, ancestor_ids a  where folks.id = a.id
      )
      select p.* from folks as p, ancestor_ids as a where p.id = a.id;
      
      

        Attachments

          Activity

            People

            Assignee:
            igor Igor Babaev
            Reporter:
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.