0030476: Consolidate the user of UPPER/LOWER to achieve case insensitive filtering

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0030476

Openbravo ERP

A. Platform

public

2015-07-31 14:21

2015-07-31 14:24

Reporter

AugustoMauch

Assigned To

AugustoMauch

Priority

normal

Severity

major

Reproducibility

have not tried

Status

new

Resolution

open

Platform

OS Version

Product Version

Target Version

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Web browser

Modules

Core

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0030476: Consolidate the user of UPPER/LOWER to achieve case insensitive filtering

Description

Although most of the times we use the UPPER function to achieve case insensitive filtering, there are a few cases where we use the LOWER function.

In some cases it is possible to define a function based index that can be used to do case insensitive filtering.

If both UPPER and LOWER are used throughout the OB codebase, it will be needed to define UPPER and LOWER function based indexes for them. For this reason it is better to use only UPPER or LOWER.

Steps To Reproduce

Look in the Openbravo codebase for instances of UPPER and LOWER. You will find that UPPER instances appear almost 10x more ofthen than LOWER ones

Proposed Solution

Additional Information

Tags

No tags attached.

Relationships

related to	feature request	0030477	new	Triage Platform Base	Generate a query with UPPER when using the ilike operator in Hibernate
related to	defect	0030488	closed	platform	API Change: Replacement of LOWER with UPPER in queries
related to	feature request	0030561	closed	AugustoMauch	Use UPPER to achieve case insensitive filtering in CustomQuerySelectorDatasource