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

Select returns outdated view information until flush tables

Details

    Description

      I'm facing the following situation. There is periodic procedure calling by event (CREATE EVENT) that modifies record and commits. There are two additional sessions (one by HeidiSQL, one by mysql command line tool) that issue select on view based on the table involved. I noticed outdated values, returned by mysql session while another session return accurate new value of datetime column.
      Then (in mysql session) I issue "flush tables" command. Then on next execution I get new value.
      This upsets me. I was expecting to get the latest column value regardless "flush tables". Is that designed behavior? Are there some system settings that affect the logic? Should I issue "flush tables" every time before issuing select?
      My environment:
      11.4.2-MariaDB
      Win64
      my.ini: autocommit=0 sql_mode=ORACLE

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          balta Tadas Balaišis created issue -
          balta Tadas Balaišis made changes -
          Field Original Value New Value
          Description I'm facing the following situation. There is periodic procedure calling by event (CREATE EVENT) that modifies record and commits. There are two additional sessions (one by HeidiSQL, one by mysql command line tool) that issue select on view based on the table involved. I noticed outdated values, returned by mysql session while another session return accurate new value of datetime column.
          Then (in mysql session) I issue "flush tables" command. Then on next execution I get new value.
          This upsets me. I was expecting to get the latest column value regardless "flush tables". Is that designed behavior? Are there some system settings that affect the logic? Should I issue "flush tables" every time before issuing select?
          My environment:
          11.4.2-MariaDB
          Win64
          my,ini: autocommit=0 sql_mode=ORACLE
          		I'm facing the following situation. There is periodic procedure calling by event (CREATE EVENT) that modifies record and commits. There are two additional sessions (one by HeidiSQL, one by mysql command line tool) that issue select on view based on the table involved. I noticed outdated values, returned by mysql session while another session return accurate new value of datetime column.
          Then (in mysql session) I issue "flush tables" command. Then on next execution I get new value.
          This upsets me. I was expecting to get the latest column value regardless "flush tables". Is that designed behavior? Are there some system settings that affect the logic? Should I issue "flush tables" every time before issuing select?
          My environment:
          11.4.2-MariaDB
          Win64
          my.ini: autocommit=0 sql_mode=ORACLE
          elenst Elena Stepanova made changes -
          Issue Type Task [ 3 ] Bug [ 1 ]
          elenst Elena Stepanova made changes -
          Fix Version/s N/A [ 14700 ]
          Resolution Not a Bug [ 6 ]
          Status Open [ 1 ] Closed [ 6 ]

          People

            Unassigned Unassigned
            balta Tadas Balaišis
            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.