From 8733ea3cf5327be4865f84f6ef3dd9294bcb2483 Mon Sep 17 00:00:00 2001 From: Ben Madore Date: Mon, 30 Jan 2017 16:11:04 -0600 Subject: [PATCH] DATACOUCH-278 - Correct table reference in repository documentation You refer to table 1 - which is the first table in THIS adoc file, but you only generate a single-page html file, so it, in fact is displayed as table 3. Original pull request: #129. --- src/main/asciidoc/repository.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/asciidoc/repository.adoc b/src/main/asciidoc/repository.adoc index c98c9d78..8eba1730 100644 --- a/src/main/asciidoc/repository.adoc +++ b/src/main/asciidoc/repository.adoc @@ -273,7 +273,7 @@ We'll only cover views to the extent to which they are needed, if you need in-de As a rule of thumb, all repository CRUD access methods which are not "by a specific key" still require a single backing view, by default `all`, to find the one or more matching entities. -IMPORTANT: This is only true for the methods directly defined by the `CrudRepository` interface (the one marked with a `*` in `Table 1.` above), since your additional methods can now be backed by N1QL. +IMPORTANT: This is only true for the methods directly defined by the `CrudRepository` interface (the one marked with a `*` in `Table 3.` above), since your additional methods can now be backed by N1QL. To cover the basic CRUD methods from the `CrudRepository`, one view needs to be implemented in Couchbase Server. It basically returns all documents for the specific entity and also adds the optional reduce function `_count`.