#367 - Polishing.

Simplified the NamingStrategy by replacing parts of it with Table and Column annotations.
This commit is contained in:
Jens Schauder
2018-05-24 09:38:07 +02:00
parent 3248cda95c
commit 0a9a8f4e60
3 changed files with 7 additions and 11 deletions

View File

@@ -14,9 +14,9 @@ This example demonstrate basic usage of JDBC based repositories.
This example demonstrates various ways to bend what the standard mapping of Spring Data JDBC can do.
* `AggregateContext.idSetting()` registers an `ApplicationListener` to implement a custom id generation strategy for `LegoSet` and `Manual`.
* `AggregateConfiguration.idSetting()` registers an `ApplicationListener` to implement a custom id generation strategy for `LegoSet` and `Manual`.
* `AggregateContext.namingStrategy()` registers a custom `NamingStrategy` in order to map property and class names to database columns and tables.
* `AggregateConfiguration.namingStrategy()` registers a custom `NamingStrategy` in order to map property and class names to database columns and tables.
* The `minimumAge` and `maximumAge` properties show a way to use types which don't have direct mapping to a SQL type, by marking them with `@Transient` and having converted properties for Spring Data JDBC to use.