Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-3805

DB migration: fix incorrect message "The database is case insensitive. Crucible requires that the database use a case sensitive collation" to reflect the current check: "The database is not Unicode. Crucible requires ..."

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Fixed
    • 2.5.3
    • User interface
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      In the Database Configuration settings (Admin > Databases), the test connection button shows an invalid message when the database is not using a Unicode encoding.

      It says:

      The database is case insensitive. Crucible requires that the database use a case sensitive collation

      whereas, to reflect the actual check, it should be:

      The database is not using Unicode. Crucible requires that the database uses a UTF8 encoding to support internalization.

      Attachments

        Issue Links

          is cloned from

          Suggestion - FE-3250 DB migration: fix incorrect message "The database is case insensitive. Crucible requires that the database use a case sensitive collation" to reflect the current check: "The database is not Unicode. Crucible requires ..."

          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. CRUC-2814 Crucible doesn't ensure its SQL DB is using case-sensitive comparisons

          • Low - Low priority issues
          • Closed

          Activity

            People

              pepoirot Pierre-Etienne Poirot (Inactive)
              9104a2602333 thybitbucket
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: