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

For unsupported statements ROW_NUMBER shows different values depending on previous events

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.7
    • Fix Version/s: 10.7
    • Component/s: Server
    • Labels:
      None

      Description

      --source include/have_innodb.inc
      --disable_abort_on_error
       
      create or replace table t (a tinyint) engine=InnoDB;
      backup stage end;
      get diagnostics condition 1 @n1 = row_number;
      insert into t values (1),(2),(1000);
      backup stage end;
      get diagnostics condition 1 @n2 = row_number;
      select 1;
      backup stage end;
      get diagnostics condition 1 @n3 = row_number;
      select @n1, @n2, @n3;
      

      bb-10.7-row_number cb9002bee36

      MariaDB [test]> select @n1, @n2, @n3;
      +------+------+------+
      | @n1  | @n2  | @n3  |
      +------+------+------+
      |    0 |    3 |    1 |
      +------+------+------+
      1 row in set (0.000 sec)
      

      It should probably be always 0.

      Same applies to various other statements, e.g. the same test case returns the same result if backup stage end is replaced by a failing drop database, or grant, etc.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              rucha174 Rucha Deodhar
              Reporter:
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:

                  Git Integration