GH-2032 - Remove duplicated documentation.

Author: michael-simons

src/main/asciidoc/appendix/custom-queries.adoc

@@ -6,6 +6,9 @@ Those come in handy if you cannot express the finder logic via derived query fun
 
 Because Spring Data Neo4j works heavily record-oriented under the hood, it is important to keep this in mind and not build up a result set with multiple records for the same "root node".
 
+TIP: Please have a look in the FAQ as well to learn about alternative forms of using custom queries from repositories, especially
+how to use custom queries with custom mappings: <<faq.custom-queries-and-custom-mappings>>.
+
 [[custom-queries.for-relationships]]
 == Queries with relationships
 

src/main/asciidoc/faq/faq.adoc

@@ -379,74 +379,6 @@ One way to do this is shown in <<domain-results>>.
 
 To use this base repository for all declared repositories enable Neo4j repositories with: `@EnableNeo4jRepositories(repositoryBaseClass = MyRepositoryImpl.class)`.
 
-[[faq.spel.custom-query]]
-== How do I use Spring Expression Language in custom queries?
-
-{spring-framework-ref}/core.html#expressions[Spring Expression Language (SpEL)] can be used in custom queries inside `:#{}`.
-This is the standard Spring Data way of defining a block of text inside a query that undergoes SpEL evaluation.
-
-The following example basically defines the same query as above, but uses a `WHERE` clause to avoid even more curly braces:
-
-[source,java,indent=0]
-[[custom-queries-with-spel]]
-.ARepository.java
-----
-include::../../../../src/test/java/org/springframework/data/neo4j/documentation/repositories/domain_events/ARepository.java[tags=spel]
-----
-
-The SpEL blocked starts with `:#{` and than refers to the given `String` parameters by name (`#pt1`).
-Don't confuse this with the above Cypher syntax!
-The SpEL expression concatenates both parameters into one single value that is eventually passed on to the <<neo4j-client>>.
-The SpEL block ends with `}`.
-
-SpEL also solves two additional problems. We provide two extensions that allow to pass in a `Sort` object into custom queries.
-Remember <<custom-queries-with-page-and-slice-examples>> from <<faq.custom-queries,custom queries>>?
-With the `orderBy` extension you can pass in a `Pageable` with a dynamic sort to a custom query:
-
-[[custom-queries-with-spel-extensions]]
-[source,java]
-.orderBy-Extension
-----
-import org.springframework.data.domain.Pageable;
-import org.springframework.data.domain.Sort;
-import org.springframework.data.neo4j.repository.Neo4jRepository;
-import org.springframework.data.neo4j.repository.query.Query;
-
-public interface MyPersonRepository extends Neo4jRepository<Person, Long> {
-
-    @Query(""
-        + "MATCH (n:Person) WHERE n.name = $name RETURN n "
-        + ":#{orderBy(#pageable)} SKIP $skip LIMIT $limit" // <.>
-    )
-    Slice<Person> findSliceByName(String name, Pageable pageable);
-
-    @Query(""
-        + "MATCH (n:Person) WHERE n.name = $name RETURN n :#{orderBy(#sort)}" // <.>
-    )
-    List<Person> findAllByName(String name, Sort sort);
-}
-----
-<.> A `Pageable` has always the name `pageable` inside the SpEL context.
-<.> A `Sort` has always the name `sort` inside the SpEL context.
-
-The `literal` extension can be used to make things like labels or relationship-types "dynamic" in custom queries.
-Neither labels nor relationship types can be parameterized in Cypher, so they must be given literal.
-
-[source,java]
-.literal-Extension
-----
-interface BaseClassRepository extends Neo4jRepository<BaseClass, Long> {
-
-    @Query("MATCH (n:`:#{literal(#label)}`) RETURN n") // <.>
-    List<Inheritance.BaseClass> findByLabel(String label);
-}
-----
-<.> The `literal` extension will be replaced with the literal value of the evaluate parameter.
-    Here it has been used to match dynamically on a Label.
-    If you pass in `SomeLabel` as a parameter to the method, `MATCH (n:``SomeLabel``) RETURN n`
-    will be generated. Ticks have been added to correctly escape values. SDN won't do this
-    for you as this is probably not what you want in all cases.
-
 [[faq.entities.auditing]]
 == How do I audit entities?