repositoryNamePrefix
The repository name prefix to use.
In case the repository name already contains the configured prefix, it will not be added twice.
Configuration Options
Option: ''
The default value of the repositoryNamePrefix
configuration option is the empty string. Setting the option to `` therefore produces the same code generated as the default configuration without any configuration option set. It produces code similar to this:
package com.example.persistence;
public class SomeRepository {
// ... rest of generated code
}
Option: ‘Database’
Changing the repositoryNamePrefix
configuration option to Database
generates the following code instead:
package com.example.persistence;
public class DatabaseSomeRepo {
// ... rest of generated code (same as above)
}
Related Options
- allowedCallPrefixes: Configures which name prefixes are allowed for statements that are calling stored procedures.
- allowedReadPrefixes: Configures which name prefixes are allowed for statements that are reading data from your database.
- allowedWritePrefixes: Configures which name prefixes are allowed for statements that are writing data to your database.
- basePackageName: The base package name for all repositories
- catchAndRethrow: Catch exceptions during SQL execution and re-throw them as RuntimeExceptions
- createConnection: Controls whether the generated code should create/open connection itself or use a given connection.
- executeBatch: Generate methods that are executed as batch
- executeBatchPrefix: The method prefix to use for generated methods that execute in a batch.
- executeBatchSuffix: The method suffix to use for generated methods that execute in a batch.
- executeOnce: Generate methods that are executed once with the given parameters
- executeOncePrefix: The method prefix to use for generated methods that execute once.
- executeOnceSuffix: The method suffix to use for generated methods that execute once.
- generateInterfaces: Generate interfaces for all repositories
- injectConverters: Toggles whether converters should be injected as constructor parameters.
- repositoryInterfacePrefix: The repository interface name prefix to use.
- repositoryInterfaceSuffix: The repository interface name suffix to use.
- repositoryNameSuffix: The repository name suffix to use.
- throwOnMultipleResults: Throw an exception in case a statement using
ReturningMode.SINGLE
produces more than 1 result. - validateMethodNamePrefixes: Validate user given names against list of allowed prefixes per type.
- writesReturnUpdateCount: Writing method which are using
ReturningMode.NONE
return the number of affected rows instead.
Tooling
Ant
In order to use YoSQL
together with Ant, take a look at the tooling documentation for Ant.
Bazel
In order to use YoSQL
together with Bazel, take a look at the tooling documentation for Bazel.
CLI
In order to use YoSQL
on the command line, take a look at the tooling documentation for CLI.
$ yosql --repositories-repository-name-prefix=configValue
As long as the name of the config option is unique across all configuration groups, you can use the shorter form:
$ yosql --repository-name-prefix=configValue
Gradle
In order to use YoSQL
together with Gradle, take a look at the tooling documentation for Gradle. The repositoryNamePrefix
setting can be configured using Gradle in Kotlin syntax like this:
plugins {
java
id("wtf.metio.yosql") version "2023.2.22"
}
yosql {
repositories {
repositoryNamePrefix.set(configValue)
}
}
or in Groovy syntax like this:
plugins {
id "java"
id "wtf.metio.yosql" version "2023.2.22"
}
yosql {
repositories {
repositoryNamePrefix = configValue
}
}
Maven
In order to use YoSQL
together with Maven, take a look at the tooling documentation for Maven. The repositoryNamePrefix
setting can be configured using Maven like this:
<build>
<plugins>
<plugin>
<groupId>wtf.metio.yosql</groupId>
<artifactId>yosql-tooling-maven</artifactId>
<version>2023.2.22</version>
<configuration>
<repositories>
<repositoryNamePrefix>configValue</repositoryNamePrefix>
</repositories>
</configuration>
</plugin>
</plugins>
</build>