Message-ID: <1754657316.2811.1369320969104.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2810_1362348511.1369320969103" ------=_Part_2810_1362348511.1369320969103 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Case insensitive search need to be improved to take advantage of st= ore implementations
= improving the search conditions
This = page represents the current plan; for discussion please ch= eck the tracker link above.
Nowadays, the CQL module does= not implement the ILIKE statement. The CQL specification only talks about = the LIKE statement so it is case-sensitive. Moreover, the GeoTool infrastru= cture (datastore, sql encoders, etc) saves this limitations with the case i= nsensitive functions which allow to lowercase/uppercase an expression. =C2= =A0
toLowerCase(myAttribute) LIKE 'blah%'
Those functions are n= ot supported at all by the sql encoders, so the filtering is performed comp= letely in memory. This approach saves the problem and works well for small = datasets. Additionally, the use of a toLowerCase or toUpperCase on an sql c= olumn will prevent using sql index with the resultant low performance probl= em.
To take advantages of this new feature some geotools components s= hould be changed.
To begin the impact analysis I copy below some comm= ent taken from our e-mail list.
This work has compl= eted, voting results were not recorded:
lac= k mandate/funds/time