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

mysql_stmt_errno() returns 0 after an error in mysql_stmt_execute()

Details

    • Bug
    • Status: Confirmed (View Workflow)
    • Critical
    • Resolution: Unresolved
    • 10.6.21, 10.11.10, 11.4.5
    • 10.11, 11.4, 11.8
    • Prepared Statements
    • None

    Description

      In my program, I use the C mariadb connector and since my upgrade of MariaDB server to the 10.11.10 version I noticed this:

      if (mysql_stmt_execute(stmt)) {
      		 
       int32_t err_code = mysql_stmt_errno(stmt);
      		 
        if (err_code == 0) {
      		 
          logger->info("This should not happen, but we are here...");
      		 
        }
      		 
      }

      I'm not sure the err_code is always 0. I know it is 0 when the statement is an INSERT and there are operations on the table like some repartitionning...

      I also noticed this when I insert a row in a table that doesn't exist.

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. CONPY-197 Uninterpretable mariadb.InterfaceError

          • Critical - Crashes, loss of data, severe memory leak.
          • Open
          relates to

          Bug - A problem which impairs or prevents the functions of the product. CONC-608 mysql_stmt_fetch() returns 1, but mysql_stmt_errno() returns 0

          • Major - Major loss of function.
          • Open

          Activity

            People

              serg Sergei Golubchik
              David David Boucher
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.