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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.11
    • Fix Version/s: 2.0.18, 3.0.7
    • Component/s: General
    • Labels:
      None
    • Environment:
      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

            People

            Assignee:
            Lawrin Lawrin Novitsky
            Reporter:
            ccalender Chris Calender
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration