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

Cursor flag set incorrectly in COM_STMT_EXECUTE response

    XMLWordPrintable

Details

    Description

      I am not certain this is a MariaDB bug. I am also at this point unable to test if it exists on MySQL. A bug has been filed with PHP, where I was using the mysqlnd client

      When you prepare a statement that is a 'CALL' statement, and the stored procedure in the 'CALL' statement uses a CURSOR internally, the COM_STMT_EXECUTE response has the SERVER_STATUS_CURSOR_EXISTS server status flag set. The documentation says this is only used with COM_STMT_FETCH, and I can't see any reason why it is indicated if a cursor was used in the stored procedure or not (regardless if the data came from the cursor, or even if a fetch was executed).

      I am not sure if it is duplicate of MDEV-17252, as that appears to be related but not identical.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. CONC-424 mysql_stmt_store_result returns empty error

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-17252 mysql_stmt_fetch error during fetch of stored procedure (with cursor) results

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Stalled

          Activity

            People

              shulga Dmitry Shulga
              rmhumphries Robert Humphries
              Votes:
              0 Vote for this issue
              Watchers:
              7 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.