From 1a32e2201705ad35000e6187509043f7b8bd6290 Mon Sep 17 00:00:00 2001 From: Jens Schauder Date: Tue, 17 Apr 2018 15:03:30 +0200 Subject: [PATCH] DATAJDBC-206 - Polishing. Removed single lined table. Original pull request: #61. --- README.adoc | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/README.adoc b/README.adoc index b8cc9214..42bf7280 100644 --- a/README.adoc +++ b/README.adoc @@ -186,14 +186,8 @@ If you are not using autoincrement-columns, you can use a `BeforeSave`-listener If you use the standard implementations of `CrudRepository` as provided by Spring Data JDBC, it will expect a certain table structure. You can tweak that by providing a https://github.com/spring-projects/spring-data-jdbc/blob/master/src/main/java/org/springframework/data/jdbc/mapping/model/NamingStrategy.java[`NamingStrategy`] in your application context. -.Optional classes of NamingStrategy -|=== -| Class | Description - -| https://github.com/spring-projects/spring-data-jdbc/blob/master/src/main/java/org/springframework/data/jdbc/mapping/model/DelimiterNamingStrategy.java[`DelimiterNamingStrategy`] -| The delimiter character implementation of NamingStrategy. The default delimiter is `_`(underscore), resulting in snake case. -|=== - +In many cases a https://github.com/spring-projects/spring-data-jdbc/blob/master/src/main/java/org/springframework/data/jdbc/mapping/model/DelimiterNamingStrategy.java[`DelimiterNamingStrategy`] +might be good basis for a custom implementation === Events