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

"S1096 Invalid information type" returned from SQLGetInfoW SQL_ODBC_API_CONFORMANCE

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 1.0.0
    • 1.0.0
    • None
    • None
    • Windows 7 Professional SP1, ODBC Management Studio 2.0.0.0, MySQL 5.5.40-0ubuntu0.14.04.1

    Description

      MariaDB ODBC Driver returns "Invalid information type" when asked for SQL_ODBC_API_CONFORMANCE. MySQL Connector/ODBC returns "SQL_OAC_LEVEL1".

      Output from ODBC trace:

      ODBCStudio f8c-f08 ENTER SQLGetInfoW
      HDBC 0x0012F050
      UWORD 9 <SQL_ODBC_API_CONFORMANCE>
      PTR 0x0281D164
      SWORD 2
      SWORD * 0x0281D160

      ODBCStudio f8c-f08 EXIT SQLGetInfoW with return code -1 (SQL_ERROR)
      HDBC 0x0012F050
      UWORD 9 <SQL_ODBC_API_CONFORMANCE>
      PTR 0x0281D164
      SWORD 2
      SWORD * 0x0281D160

      DIAG [S1096] Invalid information type (0)

      ODBCStudio f8c-f08 ENTER SQLErrorW
      HENV 0x001274F8
      HDBC 0x0012F050
      HSTMT 0x00000000
      WCHAR * 0x0281D0F4
      SDWORD * 0x0281CC7C
      WCHAR * 0x0281CC90
      SWORD 511
      SWORD * 0x0281CC84

      ODBCStudio f8c-f08 EXIT SQLErrorW with return code 0 (SQL_SUCCESS)
      HENV 0x001274F8
      HDBC 0x0012F050
      HSTMT 0x00000000
      WCHAR * 0x0281D0F4 [ 5] "S1096"
      SDWORD * 0x0281CC7C (0)
      WCHAR * 0x0281CC90 [ 24] "Invalid information type"
      SWORD 511
      SWORD * 0x0281CC84 (24)

      Attachments

        Activity

          People

            Lawrin Lawrin Novitsky
            julian.ladisch Julian Ladisch
            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.