From ac4e84dc815025ed067ede628b61d965132fb5ba Mon Sep 17 00:00:00 2001 From: Jens Schauder Date: Wed, 22 May 2019 14:19:18 +0200 Subject: [PATCH] #55 - Polishing. Minor changes to documentation in order to avoid ``s constructs as recommended by our style guide. Original pull request: #125. --- src/main/asciidoc/reference/r2dbc-fluent.adoc | 2 +- src/main/asciidoc/reference/r2dbc-sql.adoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/main/asciidoc/reference/r2dbc-fluent.adoc b/src/main/asciidoc/reference/r2dbc-fluent.adoc index 409b5088..28493e13 100644 --- a/src/main/asciidoc/reference/r2dbc-fluent.adoc +++ b/src/main/asciidoc/reference/r2dbc-fluent.adoc @@ -1,7 +1,7 @@ [[r2dbc.datbaseclient.fluent-api]] = Fluent Data Access API -You have already seen ``DatabaseClient``s SQL API that offers you maximum flexibility to execute any type of SQL. +You have already seen the SQL API of `DatabaseClient` that offers you maximum flexibility to execute any type of SQL. `DatabaseClient` provides a more narrow interface for typical ad-hoc use-cases such as querying, inserting, updating, and deleting data. The entry points (`insert()`, `select()`, `update()`, and others) follow a natural naming schema based on the operation to be run. Moving on from the entry point, the API is designed to offer only context-dependent methods that lead to a terminating method that creates and runs a SQL statement. Spring Data R2DBC uses a `R2dbcDialect` abstraction to determine bind markers, pagination support and data types natively supported by the underlying driver. diff --git a/src/main/asciidoc/reference/r2dbc-sql.adoc b/src/main/asciidoc/reference/r2dbc-sql.adoc index af88e70f..d4e8feab 100644 --- a/src/main/asciidoc/reference/r2dbc-sql.adoc +++ b/src/main/asciidoc/reference/r2dbc-sql.adoc @@ -119,7 +119,7 @@ In JDBC, the actual drivers translate question mark bind markers to database-nat Spring Data R2DBC allows you to use native bind markers or named bind markers with the `:name` syntax. -Named parameter support leverages ``R2dbcDialect``s to expand named parameters to native bind markers at the time of query execution which gives you a certain degree of query portability across various database vendors. +Named parameter support leverages a ``R2dbcDialect`` instance to expand named parameters to native bind markers at the time of query execution which gives you a certain degree of query portability across various database vendors. **** The query-preprocessor unrolls named `Collection` parameters into a series of bind markers to remove the need of dynamic query creation based on the number of arguments.