From ca1d92c48c1129c9ed6b4dc155e88e43e375e082 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Sebastian=20Ho=C3=9F?= Date: Fri, 22 Apr 2022 09:03:07 +0200 Subject: [PATCH] remove dead links --- yosql-website/content/persistence/_index.md | 2 +- yosql-website/content/tooling/_index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/yosql-website/content/persistence/_index.md b/yosql-website/content/persistence/_index.md index efb5dccc..9676c76e 100644 --- a/yosql-website/content/persistence/_index.md +++ b/yosql-website/content/persistence/_index.md @@ -8,4 +8,4 @@ menu: `YoSQL` supports multiple persistence APIs to interact with a database. We recommend that you pick the one that is already available in your project. In case you are starting fresh, `YoSQL` will default to the JDBC implementation because it requires no external dependencies and thus your project should be able to compile the generated code just fine. Some `YoSQL` tooling like the Maven plugin might auto-detect certain settings in your project to make your life easier, however you are always in full control and can change very aspect of the generated code. -Take a look at the available [configuration](/configuration/) options to adapt the generated code according to your needs. In order to monitor execution of your SQL statements, we recommend enabling one of the supported [logging](/logging/) APIs to add log output to the generated code. Read the [SQL](/sql/) section to learn how to write SQL statements in a `YoSQL`-enabled project. +Take a look at the available [configuration](/configuration/) options to adapt the generated code according to your needs. In order to monitor execution of your SQL statements, we recommend enabling one of the supported logging APIs to add log output to the generated code. Read the [SQL](/sql/) section to learn how to write SQL statements in a `YoSQL`-enabled project. diff --git a/yosql-website/content/tooling/_index.md b/yosql-website/content/tooling/_index.md index 28426e03..4a2ee55b 100644 --- a/yosql-website/content/tooling/_index.md +++ b/yosql-website/content/tooling/_index.md @@ -10,7 +10,7 @@ This part of the documentation is intended for **developers** looking for inform In its default configuration, `YoSQL` will try to generate as much code as possible, and you are expected to configure the generated code so that it matches the requirements of your project. Some `YoSQL` tools will try to auto-detect certain settings, e.g. the Maven plugin will look at existing dependencies, and the configuration of the compiler plugin in order to create a configuration for your project automatically. Take a look at the [configuration](/configuration/) section in order to see all available configuration options in case you want to change something. -All `YoSQL` tools support multiple [persistence](/persistence/) and [logging](/logging/) APIs. Try to use the same APIs that are already available in your project, in order to keep the number of dependencies as low as possible (zero). +All `YoSQL` tools support multiple [persistence](/persistence/) and logging APIs. Try to use the same APIs that are already available in your project, in order to keep the number of dependencies as low as possible (zero). Once your initial setup is complete, it's time to write [SQL](/sql/) statements. There is no upper limit imposed by `YoSQL` on how many statements there can be per generated repository, however Java has a hard limit of 65535 methods per class. We recommend splitting your statements according to the domain objects in your projects, e.g. all statements that are related to a single class should go in one repository, but you a free to choose whatever structure best fits your project. -- 2.11.4.GIT