Thanks for the feedback.
{param} should use in all caess.
I create a test for you issue and report back to you.
Cheers
Michael
Am 24.10.2011 um 14:41 schrieb Tero Paananen:
> I just upgraded to Spring Data Graph for Neo4J 2.0.0.M1 and it
> looks like certain things changed for the worse for my needs.
>
> Just looking for clarification of whether these changes are
> permanent or to be addressed before final release.
>
> I'm using Cypher queries defined in Repository classes, e.g.:
>
> @Repository
> public interface CustomRepository extends GraphRepository<User> {
> @Query(value = "start u = node:user(name = '%foo') match
> (u)-[:KNOWS*1..%depth]->() return u", type = QueryType.Cypher)
> Iterable<User> getConnections(@Param("foo") String foo, @Param("depth")
> Integer depth);
> }
>
> This used to work just fine in 1.1.0.RELEASE.
>
> In 2.0.0.M01 %foo should be {foo} and %depth produces a syntax
> error regardless of whether I specify it with %depth or {depth}.
> Same with skip and limit instructions:
>
> .. return u skip %skip limit %limit
>
> used to work just fine, however
>
> .. return u skip {skip} limit {limit}
>
> no longer works.
>
> I know I could probably replicate this behavior using the
> Neo4JTemplate functionality, but I'm not sure that's actually
> a better way of doing that, considering how convenient it is
> to create queries with the @Query annotation.
>
> Your thoughts? And what would be my best options for alternatives
> at this point?
>
> Thanks!
>
> -TPP
> _______________________________________________
> Neo4j mailing list
> [email protected]
> https://lists.neo4j.org/mailman/listinfo/user
_______________________________________________
Neo4j mailing list
[email protected]
https://lists.neo4j.org/mailman/listinfo/user
