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

Make executables MariaDB named

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Fix Version/s: 10.5.2
    • Component/s: OTHER
    • Labels:
      None

      Description

      In 10.4 mariadb named symlinks were added to make it possible to run the the tools for MariaDB. For example instead of writing mysql to start the client one can write mariadb, or mariadb-dump instead of mysqldump. More details on what was done in 10.4 can be found in the task MDEV-17591.

      In 10.5 we're taking the next step and flipping the logic, i.e. so that the binaries will actually be named mariadb-something and there will be a symlink for the corresponding mysql command.

        Attachments

          Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-22003 mysql_config disappeared from 10.5 (e.g. binary tarball or source build)

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-22009 main.mysqlhotcopy_myisam cannot find mysqlhotcopy tool

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-22010 use executables MariaDB named in scripts

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

          Task - A task that needs to be done. MDEV-22023 fix manpages to use mariadb* executable names

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-22214 Windows: crash when mariadbd.exe tries to load plugin which is linked to mysqld.exe

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-22569 Startup scripts in 10.5 still start "mysqld" instead of "mariadbd"

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-29615 mtr to use mariadb names

          • Major - Major loss of function.
          • Open
          relates to

          Task - A task that needs to be done. MDEV-17591 Create MariaDB named commands

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-21298 mariabackup doesn't read from the [mariadbd] and [mariadbd-X.Y] server option groups from configuration files

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-21301 mariabackup doesn't read [mariadb-backup] option group in configuration file

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-29614 mariadb-upgrade calls mysql and mysql-check rather than mariadb/mariadb-check

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-17812 Use MariaDB in error messages instead of MySQL

          • Major - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              ratzpo Rasmus Johansson (Inactive)
              Reporter:
              ratzpo Rasmus Johansson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 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.