Uploaded image for project: 'Percona Server'
  1. Percona Server
  2. PS-5494

MyRocks limitations page incorrectly refers to binary rather than case-sensitive collations

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Confirmation
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Documentation, MyRocks
    • Labels:
      None

      Description

      https://www.percona.com/doc/percona-server/5.7/myrocks/limitations.html currently says the following:

      *_bin (e.g. latin1_bin) or binary collation should be used on CHAR and VARCHAR indexed columns. By default, MyRocks prevents creating indexes with non-binary collations (including latin1). You can optionally use it by settingrocksdb_strict_collation_exceptions to t1 (table names with regex format), but non-binary covering indexes other than latin1 (excluding german1) still require a primary key lookup to return the CHAR or VARCHAR column.

      I think it should say "case-sensitive" instead of "binary" and "case-insensitive" instead of "non-binary". For example, see:

      All of those documents refer to case (in)sensitivity of collations, rather than the binary / non-binary ones. Which I think is more precise.

        Smart Checklist

          Attachments

            Activity

              People

              • Assignee:
                patrick.birch Patrick Birch
                Reporter:
                akopytov Alexey Kopytov
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: