Help:$smwgFieldTypeFeatures

is a configuration parameter that sets relational database specific field type features. The configuration parameter was introduced in .CiteRef::gh:smw:2499CiteRef::gh:smw:2536

Default setting
This means that by default no relational database specific field type features will be enabled.

Available options

 * – Disables features to database field types, identical to.
 * CiteRef::gh:smw:1912CiteRef::gh:smw:2499 – Modifies selected search fields to use a case insensitive collation by switching from " " to a collated " ". This may even require an additional extension (e.g. PostgreSQL requires " ") on non MySQL related database systems. Therefore it is disabled by default. If enabled, the setting will replace selected " " types with " ". The latter has been defined as follows:
 * - MySQL:
 * - PostgreSQL:
 * - SQLite:, but this may not work and needs a special solutionCiteRef::sqlite:ft:caseinsensitivelike


 * CiteRef::gh:smw:2536 – Extends the size to 300 characters for text pattern match fields ( and  ). By default, those fields are limited to 72 characters that limits search depth in exchange for index size and performance. Extending fields to 300 allows to run " "/" " matching on a larger text body without relying on a full-text index but an increased index size could potentially carry a performance penalty when the index cannot be kept in memory.

Changing the default setting
To modify the setting to this configuration parameter, add one of the following lines to your "LocalSettings.php" file after the  call:


 * Enable case insensitive matching for properties of e.g., , and  (blob types, i.e. strings or text)


 * Extend searchable field length to 300 charactersCiteRef::so:3489041 of e.g., and  (blob types, i.e. strings or text except for pages)


 * Combine both options to make a long field type also case insensitive

Example
See also the related example of  showing and commenting on expected results. See also this issue comment.CiteRef::gh:smw:2499:307624826