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

FIXED: Context Replay: "Field doesn't have default value" error

    XMLWordPrintable

Details

    • Bug
    • Status: In Progress (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • 13.0
    • None
    • None

    Description

      In MDEV-39368, testing with --replay-server produces numerous failures like this:

      ReplayTest: Query error: Field 'name' doesn't have a default value
      ReplayTest: In included file "./include/common-tests.inc":
      ReplayTest: included from /optane/dev-git2/13.0-context-replay/mysql-test/main/pool_of_threads.test at line 17:
      ReplayTest: At line 1477
      

      CURRENT_TEST: main.pool_of_threads
      --- /optane/dev-git2/13.0-context-replay/mysql-test/main/pool_of_threads.result 2026-04-24 13:53:12.173385038 +0300
      +++ /optane/dev-git2/13.0-context-replay/mysql-test/main/pool_of_threads.reject 2026-04-24 21:29:21.172184421 +0300
      @@ -628,9 +628,7 @@
       fld3   period
       breaking       1001
       explain select fld3,period from t2,t3 where t2.fld1 = 011401 and t3.t2nr=t2.fld1 and 1001 = t3.period;
      -id     select_type     table   type    possible_keys   key     key_len ref     rows    Extra
      -1      SIMPLE  t2      const   fld1    fld1    4       const   1
      -1      SIMPLE  t3      const   PRIMARY,period  PRIMARY 4       const   1
      +ReplayTest: Query error: Field 'name' doesn't have a default value
       select fld3,period from t2,t1 where companynr*10 = 37*10;
      

      Attachments

        Issue Links

          Activity

            People

              psergei Sergei Petrunia
              psergei Sergei Petrunia
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.