Spring/spring-data-relational
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

DATAJDBC-206 - Polishing.

Browse Source 
Removed single lined table.

Original pull request: #61.
This commit is contained in:
Jens Schauder
2018-04-17 15:03:30 +02:00
parent 0b6354eb47
commit 1a32e22017
1 changed files with 2 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.adoc
View File

@@ -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