Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-30431

No deprecation message shown for mysql* exes for Windows

Details

    Description

      Windows testing for MDEV-29582 (451f63c7) showed that the mysql deprecation message was not seen when running mysql* executables.

      Building the binaries (following these instructions ) showed hard links existing, but not the deprecation message:

      PS C:\Users\sepol\mariadb\server\bld\client\RelWithDebInfo> fsutil hardlink list .\mariadb.exe
      		 
      \Users\sepol\mariadb\server\bld\client\RelWithDebInfo\mysql.exe
      		 
      \Users\sepol\mariadb\server\bld\client\RelWithDebInfo\mariadb.exe
      		 
      PS C:\Users\sepol\mariadb\server\bld\client\RelWithDebInfo> ./mysql.exe --version
      		 
      C:\Users\sepol\mariadb\server\bld\client\RelWithDebInfo\mysql.exe from 11.0.0-MariaDB, client 15.2 for Win64 (AMD64), source revision 451f63c7fb859f56436333464bb430e98480f305

      The ZIP package mysql executables (which are not hard linked, as expected) also do not show the deprecation message:

      PS C:\Users\sepol\mariadb\zip\mariadb-11.0.0-winx64\mariadb-11.0.0-winx64\bin> ./mysql.exe --version
      		 
      C:\Users\sepol\mariadb\zip\mariadb-11.0.0-winx64\mariadb-11.0.0-winx64\bin\mysql.exe from 11.0.0-MariaDB, client 15.2 for Win64 (AMD64), source revision 451f63c7fb859f56436333464bb430e98480f305

      Ultimately MDEV-29582 serves as another method to alert users of the impending change to remove MySQL names, but Windows users would not be getting the same warning as Linux users if the same change is occurring for Windows.

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. MDEV-29582 deprecate mysql* names

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            angelique.sklavounos Angelique Sklavounos (Inactive) added a comment - - edited

            In general (for the distant future of MDEV-30201), to me it is confusing to keep the mysql aliases (hard links or copies) with the Windows builds while also wanting to put the message across that they are diverging products, but I might be unaware of some technical knowledge of Windows, or something else, that necessitates the aliases being there. For instance, I understand wanting to allow users to be able to still use both at the same time - but the aliases are not the latest MySQL. If the aliases still need to be there for whatever reason to allow the separate installation of MySQL, then I would understand that.

            angelique.sklavounos Angelique Sklavounos (Inactive) added a comment - - edited In general (for the distant future of MDEV-30201 ), to me it is confusing to keep the mysql aliases (hard links or copies) with the Windows builds while also wanting to put the message across that they are diverging products, but I might be unaware of some technical knowledge of Windows, or something else, that necessitates the aliases being there. For instance, I understand wanting to allow users to be able to still use both at the same time - but the aliases are not the latest MySQL. If the aliases still need to be there for whatever reason to allow the separate installation of MySQL, then I would understand that.

            People

              danblack Daniel Black
              angelique.sklavounos Angelique Sklavounos (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.