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

System versioning doesn't support correct work for engine=connect and doesn't always give any warnings/errors

    XMLWordPrintable

Details

    • Bug
    • Status: Confirmed (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.3, 10.4, 10.5, 10.6, 10.7, 10.8, 10.9
    • 10.4, 10.5, 10.6
    • Versioned Tables
    • None

    Description

      If add for engine=connect "system versioning" there is no any warnings/errors on creating table and inserting data, but "select" gives an empty result, "update" doesn't change value and "delete" fails with error:

      Test:

      create table t2 (
        x int,
        y int
      ) engine=connect table_type=FIX file_name='test.txt' with system versioning;
       
      insert into t2 values (1,1),(2,2),(3,3),(4,4),(5,5);
      select * from t2;
       
      update t2 set x=10 where y=4;
      select * from t2;
      delete from t2 where x=1;
      select * from t2;
       
      drop table t2;
      

      Result:

      create table t2 (
      x int,
      y int
      ) engine=connect table_type=FIX file_name='/test.txt' with system versioning;
      insert into t2 values (1,1),(2,2),(3,3),(4,4),(5,5);
      select * from t2;
      x	y
      update t2 set x=10 where y=4;
      select * from t2;
      x	y
      delete from t2 where x=1;
       
      mysqltest: At line 11: query 'delete from t2 where x=1' failed: ER_CRASHED_ON_USAGE (1194): Table 't2' is marked as crashed and should be repaired
      

      Attachments

        Issue Links

          Activity

            People

              midenok Aleksey Midenkov
              lstartseva Lena Startseva
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.