[ https://issues.apache.org/jira/browse/SYNCOPE-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15697153#comment-15697153 ]
ASF GitHub Bot commented on SYNCOPE-975: ---------------------------------------- GitHub user gonzalad opened a pull request: https://github.com/apache/syncope/pull/42 SYNCOPE-975: Search case insensitive ilike operator triggers search validation Using ilike in a search triggers search field validation. It shouldn't be triggered. This results in Syncope returning 0 records. For instance: username=~*test*;(emails=~*test.com*) tries to validate email *test.com*, which isn't a valid email You can merge this pull request into a Git repository by running: $ git pull https://github.com/gonzalad/syncope SYNCOPE-975 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/syncope/pull/42.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #42 ---- commit 42a9998e7d52d5b725f34e1b3151c4522917e27a Author: gonzalad <adr_gonza...@yahoo.fr> Date: 2016-11-26T02:41:55Z SYNCOPE-975: ilike triggers search validation Using ilike in a search triggers search field validation. It shouldn't be triggered. This results in Syncope returning 0 records. For instance: username=~*test*;(emails=~*test.com*) tries to validate email *test.com*, which isn't a valid email ---- > Search case insensitive ilike operator triggers search validation > ----------------------------------------------------------------- > > Key: SYNCOPE-975 > URL: https://issues.apache.org/jira/browse/SYNCOPE-975 > Project: Syncope > Issue Type: Bug > Reporter: gonzalad > Priority: Minor > > Follow-up for SYNCOPE-971. > Using ilike in a search triggers search field > validation. It shouldn't be triggered. > This results in Syncope returning 0 records. > For instance: username=~*test*;(emails=~*test.com*) > tries to validate email *test.com*, which isn't > a valid email > Sorry for the bug ! -- This message was sent by Atlassian JIRA (v6.3.4#6332)