Details

    Description

      A few minor issues in the catalogs documentation:

      1. The documentation mentions the access method is 'catalog/db', where in reality it is 'catalog.db'.
      2. The 'mariadb-install-db' documentation says the catalog options are in 11.3
      3. There is mention of `use-catalogs`, for MariaDB Server, but the option is `catalogs`. I think it is also implicit anyway (I haven't fully tested this).

      Attachments

        Issue Links

          Activity

            greenman Ian Gilfillan added a comment -

            Issue 2 is fixed.
            For issue 1, not having something to test yet, can you clarify if all instances of "catalogs/" should be replaced with "catalogs." in https://mariadb.com/kb/en/catalogs-overview/

            greenman Ian Gilfillan added a comment - Issue 2 is fixed. For issue 1, not having something to test yet, can you clarify if all instances of "catalogs/" should be replaced with "catalogs." in https://mariadb.com/kb/en/catalogs-overview/

            greenman Monty should be able to give you access. Yes, using "catalog/database" has not been implemented. Although "catalog/database" is what the path is to the database on disk, so be wary in case there is any disk path related things in there.

            TheLinuxJedi Andrew Hutchings (Inactive) added a comment - greenman Monty should be able to give you access. Yes, using "catalog/database" has not been implemented. Although "catalog/database" is what the path is to the database on disk, so be wary in case there is any disk path related things in there.

            People

              greenman Ian Gilfillan
              TheLinuxJedi Andrew Hutchings (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.