I've tried to reproduce this directly in Cypher, and through SDN, but I
haven't been able to. I will spend some more time on this tomorrow. If it's
possible for you to create a minimal test that reproduces the problem, it
would very helpful.
Andrés
On Thu, Nov 17, 2011 at 8:45 PM, Tero Paananen w
>> @Query(value = "start n = node(1) match (n)-[:KNOWS]->(c) where c.a =~
>> /.*?{foo}.*?/ return c", type = QueryType.Cypher)
>> Page getConnectedNodes(@Param("foo") String foo, Pageable pageable);
>>
>
> The regular expression can either be provided through a parameter, or
> inlined in the query.
On Thu, Nov 17, 2011 at 6:14 PM, Tero Paananen wrote:
> @Query(value = "start n = node(1) match (n)-[:KNOWS]->(c) where c.a =~
> /.*?{foo}.*?/ return c", type = QueryType.Cypher)
> Page getConnectedNodes(@Param("foo") String foo, Pageable pageable);
>
The regular expression can either be provided
Another regular expression related issue in Cypher. 1.5 GA.
I'm using repositories extensively in my application. I'm extending the
queries defined by the repository interfaces with my own using the @Query
annotation.
It seems as if using parametrized regular expressions in these queries
isn't wo
4 matches
Mail list logo