From version 6.6.0.0 of KonaKart it is possible to configure case-insensitive searching, for selected attributes, for databases that don't support case insensitive searching by default (such as PostgreSQL, Oracle and DB2). For the Admin App, the case-sensitivity configuration is defined using the File-Based Configuration mechanism provided in the Business and Enterprise Editions of KonaKart.

These particular settings make no difference for databases that use case insensitive searching by default (such as MySQL).

The File-Based Configuration is set in the properties file called konakartadmin_gwt.properties as follows:

#----------------------------------------------------------------------------
# Use this to define which search fields case should be ignored 
# (default is false = case is not ignored)

fbc.kk_panel_customers.first_name_ignore_case              = true
fbc.kk_panel_customers.last_name_ignore_case               = true
fbc.kk_panel_customers.email_address_ignore_case           = true
fbc.kk_panel_customers.street_address_ignore_case          = true
fbc.kk_panel_customers.street_address1_ignore_case         = true
fbc.kk_panel_customers.postcode_ignore_case                = true
fbc.kk_panel_customers.city_ignore_case                    = true

fbc.kk_panel_products.search_ignore_case                   = true
fbc.kk_panel_products.sku_ignore_case                      = true
                  

You can choose to set "ignore case" on all of the attributes supported or just a subset of them.

All Editions of KonaKart (Community, Business and Enterprise) support this case insensitive search possibility through the APIs because the AdminProductSearch and AdminCustomerSearch have attributes that define the case-insensitivity for the respective attributes.

Before setting these particular "ignore case" settings please pay attention to the impact on performance that might occur. You are most likely to get better performance if you do not set "ignore Case" to "true".

There are other techniques to achieve case-insensitive searching in those databases that don't support this by default. Refer to database-specific instructions if you choose to take this alternative option.

For example, with DB2 you can define the case sensitivity behaviour when ordering results by setting the database collating sequence. In Oracle you can set case-sensitivity using the NLS_COMP and NLS_SORT configuration variables.