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

Trying to create a file dsn causes odbc administrator to crash

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 3.0.5
    • 3.0.6, 2.0.18
    • General
    • None
    • Windows 7 Professional 64bit
      Windows 10 Pro

    Description

      When creating a file dsn on Windows 7, after clicking finish, ODBD Administrator fails to handle an exception in the ODBC Connector and crashes.

      In Windows 10, the connector exception is handled resulting in the message: "The File Data Source was not saved."

      The error occurs in both the 32 and 64 bit ODBC Administrators.

      Attachments

        Activity

          Thank you for your report. I don't think we support file DSN's, but that is not a reason to crash other applications, anyway

          Lawrin Lawrin Novitsky added a comment - Thank you for your report. I don't think we support file DSN's, but that is not a reason to crash other applications, anyway

          Commit 8912f9f has been pushed to odbc-3.0 and master branches(yet to be merged into odbc-2.0).
          I don't have the Win7 to test, but on Win10 everything works fine with FileDSNs now(with the fix). And I think it should be fine on Win7 as well.

          Lawrin Lawrin Novitsky added a comment - Commit 8912f9f has been pushed to odbc-3.0 and master branches(yet to be merged into odbc-2.0). I don't have the Win7 to test, but on Win10 everything works fine with FileDSNs now(with the fix). And I think it should be fine on Win7 as well.

          People

            Lawrin Lawrin Novitsky
            immortal Martin Lane
            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.