Spring Data Relational
The primary goal of the Spring Data project is to make it easier to build Spring-powered applications that use data access technologies. Spring Data Relational offers the popular Repository abstraction based on JDBC.
It aims at being conceptually easy. In order to achieve this it does NOT offer caching, lazy loading, write behind or many other features of JPA. This makes Spring Data JDBC a simple, limited, opinionated ORM.
Implementation of CRUD methods for Aggregates.
Support for transparent auditing (created, last changed)
Events for persistence events
Possibility to integrate custom repository code
JavaConfig based repository configuration by introducing
Integration with MyBatis
<dependency> <groupId>org.springframework.data</groupId> <artifactId>spring-data-jdbc</artifactId> <version>1.1.0.BUILD-SNAPSHOT</version> </dependency>
Spring Data Relational ships with multiple modules:
Spring Data Relational: Common infrastructure abstracting general aspects of relational database access.
Spring Data JDBC: Repository support for JDBC-based datasources.
There are also examples in the Spring Data Examples project.
A very good source of information is the source code in this repository.
Especially the integration tests (if you are reading this on github, type
t and then
We are keeping an eye on the (soon to be created) spring-data-jdbc tag on stackoverflow.
If you think you found a bug, or have a feature request please create a ticket in our issue tracker.
Building from Source
You don’t need to build from source to use Spring Data Relational (binaries in repo.spring.io). If you want to try out the latest and greatest, Spring Data Relational can be easily built with Maven. You also need JDK 1.8.
$ mvn clean install
Fast running tests
Fast running tests can be executed with a simple
$ mvn test
This will execute unit tests and integration tests using an in-memory database.
Running tests with a real database
In order to run the integration tests against a specific database you need to have a local Docker installation available, and then execute.
$ mvn test -Dspring.profiles.active=<databasetype>
This will also execute the unit tests.
Currently the following databasetypes are available:
hsql (default, does not require a running database)
Run tests with all databases
$ mvn test -Pall-dbs
This will execute the unit tests, and all the integration tests with all the databases we currently support for testing. Running the integration-tests depends on Docker.
Contributing to Spring Data Relational
Here are some ways for you to get involved in the community:
Get involved with the Spring community by helping out on Stackoverflow for Spring Data JDBC by responding to questions and joining the debate.
Create JIRA tickets for bugs and new features and comment and vote on the ones that you are interested in.
Github is for social coding: if you want to write code, we encourage contributions through pull requests from forks of this repository. If you want to contribute code this way, please reference a JIRA ticket as well, covering the specific issue you are addressing.
Watch for upcoming articles on Spring by subscribing to spring.io.
Before we accept a non-trivial patch or pull request we will need you to sign the Contributor License Agreement. Signing the contributor’s agreement does not grant anyone commit rights to the main repository, but it does mean that we can accept your contributions, and you will get an author credit if we do. If you forget to do so, you’ll be reminded when you submit a pull request. Active contributors might be asked to join the core team, and given the ability to merge pull requests.