Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-4984

JdbcStringBasedStore with MySQL sets up column that uses case-insensitive comparisons for keys

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Unresolved
    • Major
    • None
    • None
    • None
    • None

    Description

      By default MySQL performs case-insensitive comparisons. This results in a problem when Infinispan entries use Strings that are distinct only in case-sensitive ways, since by default Infinispan's JdbcStringBasedStore (and maybe JdbcBinaryCacheStore) use VARCHAR(255) for the default idColumn type.

      This can of course be corrected in the Infinispan configuration. Rather than specifying this (which is equivalent to the default):

      <idColumn name="ID_COLUMN" type="VARCHAR(255)"/>

      the following can be specified instead:

      <idColumn name="ID_COLUMN" type="VARCHAR(255) CHARACTER SET utf8 COLLATE utf8_unicode_ci"/>

      This will make MySQL perform case-sensitive comparisons and will work for all string keys.

      This enhancement request asks that the Infinispan JDBC-based stores use this by default so that it works automatically for MySQL users.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. ISPN-4125 ClassCastException if cache.keyset() is invoked for a string-keyed-jdbc-store in C/S mode

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ISPN-4159 DefaultTwoWayKey2StringMapper encodes objects to strings in a manner that is incompatible with string handling of some databases

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) MODE-2363 NodeTypeManager gets confused when using case-sensitive nodetypes on SQL storage

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              remerson@redhat.com Ryan Emerson
              rhauch Randall Hauch (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: