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

When C/ODBC is upgraded on Windows, allow existing data sources to be copied

Details

    • Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 3.1.1
    • 3.1.2
    • General
    • None

    Description

      If a user upgrades to a new major release of MariaDB Connector/ODBC (e.g. MariaDB Connector/ODBC 3.0 to MariaDB Connector/ODBC 3.1), then Driver Manager will consider the new version to be "different" driver. The user will have to recreate their existing data source in Windows ODBC Data Source Administrator.

      To save users from the hassle, it may be beneficial to implement a way to copy existing data sources when a user upgrades to a new major release of MariaDB Connector/ODBC. It should probably be optional.

      Maybe the MSI installer could ask the user if they wanted to copy existing data sources during the installation process.

      Attachments

        Activity

          Lawrin Lawrin Novitsky added a comment -

          The last page of the installation dialog has a checkbox. If checked, after clicking the "Finish" button, installer will start utility, that will change all User DNS's, referencing old connector version, to reference the newly installed one.

          Lawrin Lawrin Novitsky added a comment - The last page of the installation dialog has a checkbox. If checked, after clicking the "Finish" button, installer will start utility, that will change all User DNS's, referencing old connector version, to reference the newly installed one.

          People

            Lawrin Lawrin Novitsky
            GeoffMontee Geoff Montee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.