jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-56) allow case insensitive searches
Date Mon, 04 Apr 2005 14:54:19 GMT
     [ http://issues.apache.org/jira/browse/JCR-56?page=history ]
Marcel Reutegger resolved JCR-56:

    Resolution: Fixed

Extended syntax of XPath jcrfn:contains and SQL contains() to accept a second argument.

jcrfn:contains accepts a property name or a '.', whereas the SQL contains function accepts
a property name or a '*'.

//*[jcrfn:contains(., 'foo')
SELECT * FROM nt:base WHERE CONTAINS(*, 'foo')
 -> returns all nodes that have a property that contains 'foo'

//*[jcrfn:contains(@title, 'foo')]
SELECT * FROM nt:base WHERE CONTAINS(title, 'foo')
 -> returns all nodes that contain the word 'foo' in a title property

Jackrabbit currently still support the one argument version of the contains function. But
support will probably be removed with the next version (0.16.4?) of the JCR spec.

SVN revision: 160047

> allow case insensitive searches
> -------------------------------
>          Key: JCR-56
>          URL: http://issues.apache.org/jira/browse/JCR-56
>      Project: Jackrabbit
>         Type: New Feature
>   Components: sql
>     Reporter: Raphael Wegmueller
>     Assignee: Marcel Reutegger
>     Priority: Minor

> would be nice to be able to search specific properties like a fulltext search, e.g. with
an ignore-case flag, so you could find a subset of the results of
>   select * from nt:base where contains('bla')
> using something like
>   select * from nt:base where jcr:bla like '%bla%'
> (currently, the value must contain 'bla' exactly as it is to be found by the second query)
> i suggest to extend the contains function with an additional argument for the property
to search in, e.g.
>   select * from nt:base where contains('bla',jcr:bla)
> this could then also easily be used in XPath.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message