Uploaded image for project: 'MariaDB Connector/ODBC'
  1. MariaDB Connector/ODBC
  2. ODBC-177

Deadlock error not reported correctly back to client application when using Connector/ODBC

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.0.11
    • 2.0.18, 3.0.7
    • General
    • None
    • MariaDB Connector/ODBC 2.0.11 64-bit

    Description

      Deadlocks in nested stored procedures are not propagating the deadlock error back to the application properly when using Connector/ODBC.

      Attached is an ODBC Trace when calling a SP. You can see that the call to NextResult() returned SQL_NO_DATA_FOUND, and not the error.

      And per Georg:

      "Afaik the problem is here: https://github.com/MariaDB/mariadb-connector-odbc/blob/master/ma_result.c#L95

      if mysql_stmt_next_result failed, the function should return an error. SQL_NO_DATA is ok, if field_count is zero"

      Attachments

        Activity

          I guess that is not about deadlocks, and nested procedures, but more generally - for any query returning > 1 results, and where 2nd or later statement's result is an error

          Lawrin Lawrin Novitsky added a comment - I guess that is not about deadlocks, and nested procedures, but more generally - for any query returning > 1 results, and where 2nd or later statement's result is an error

          The fix and the testcase have been pushed into odbc-3.0
          Commit 871f483 (will be diff in odbc-2.0)

          Lawrin Lawrin Novitsky added a comment - The fix and the testcase have been pushed into odbc-3.0 Commit 871f483 (will be diff in odbc-2.0)

          People

            Lawrin Lawrin Novitsky
            ccalender Chris Calender (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.