1,127
edits
Difference between revisions of "Case Insensitive Search"
m
→Resulting Issues
m (Added article on DB2 case insensitvity.) |
|||
| Line 19: | Line 19: | ||
=== Resulting Issues === | === Resulting Issues === | ||
If the data you're indexing, searching for, and storing in CMOD requires case-sensitivity, there is no good solution to this issue, and end users should be instructed to pay close attention to proper capitalization. | If the data you're indexing, searching for, and storing in IBM CMOD requires case-sensitivity, there is no good solution to this issue, and end users should be instructed to pay close attention to proper capitalization. | ||
The capitalization of a field cannot be changed after an Application Group has been created. It *is* possible to update database tables manually, but this is not supported by IBM. | The capitalization of a field cannot be changed after an Application Group has been created. It *is* possible to update database tables manually, but this is not supported by IBM. | ||
| Line 27: | Line 27: | ||
Storing characters in Mixed Case will reduce compression inside database tables, as "smith", "Smith", and "SMITH" are all different, and must be stored individually. | Storing characters in Mixed Case will reduce compression inside database tables, as "smith", "Smith", and "SMITH" are all different, and must be stored individually. | ||
An IBM Developerworks article exists on [https://www.ibm.com/developerworks/data/library/techarticle/0203adamache/0203adamache.html implementing case-insensitivy in DB2], but it's not clear how this can be integrated into Content Manager OnDemand to provide the desired functionality. | An IBM Developerworks article exists on [https://www.ibm.com/developerworks/data/library/techarticle/0203adamache/0203adamache.html implementing case-insensitivy in DB2], but it's not clear how this can be integrated into IBM Content Manager OnDemand to provide the desired functionality. | ||