Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-1600

maxscale it seen to not coop well with lower-case-table-names=1 on cnf

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.1.11
    • 2.1.14
    • Authenticator
    • None
    • galera cluster + 2 maxscale HA keepalive
    • MXS-SPRINT-50

    Description

      When Mariadb configuration file has the option lower-case-table-names=1 , it seen maxscale do not consider from connection string that the case sensitive can be ignored.

      Result is not detecting the presence of a schema if the case sensitive is not respect.

      lower_case_table_names =1 : Table names are stored in lowercase on disk and name comparisons are not case-sensitive. MySQL converts all table names to lowercase on storage and lookup. This behavior also applies to database names and table aliases.

      Attachments

        Activity

          People

            markus makela markus makela
            massimo.disaro Massimo
            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.