GA release of Spring Data JDBC Extensions 1.0 with Querydsl and advanced Oracle JDBC

Dear Spring Community,

We are pleased to announce the availability of the 1.0 GA release of the Spring Data JDBC Extensions project providing Querydsl and advanced Oracle Database support!

The Spring Data JDBC Extensions project was created to provide additional support for vendor specific JDBC extensions as well as new approaches to working with JDBC like Querydsl. The bulk of the support consists of code ported from the SpringSource project "Advanced Pack for Oracle Database" that was available for support subscription customers. We are now making this code available to all Spring users and any new developments will be made in the Spring Data JDBC Extensions project.

An example of how to use the Spring Data JDBC Querydsl features is available in Chapter 5 in the new O'Reilly book Spring Data and also in the book's example project.

To learn more about the project, visit the Spring Data JDBC Extensions Homepage.

We are looking forward to your feedback on the forum or in the issue tracker.

Downloads | JavaDocs | Reference Documentation | Changelog

thanks for updating us with the updated version of it. Thanks a lot.

Natalia
www.groffr.com

Can Spring-JDBC-ROMA (http://serkan-ozal.github.io/spring-jdbc-roma/) be a good feature for Spring Data JDBC Extensions?

Hi,

I think this could potentially be a feature of the JDBC EXtensions project. I'm also looking at the "Spring Data JDBC Repository" project (https://github.com/nurkiewicz/spring...dbc-repository). Maybe a combination of both could be interesting but I'd have to look in more detail. We'll probably have more time in the June-July timeframe to look at these new features.

Hi,

Sounds great.
I am also thinking of working on generic JDBC implementation.
Combining my row-mapper with Spring Data JDBC Repository can be a great Spring module.

In addition, I am currently working on new features:

1. Column name definition policy support:

• Explicit Column Name Definition Policy
• Custom Column Name Definition Policy
• Field-Table Column Name String Similarity Based Auto Column Name Definition Policy

2. SQL based object relation support by specifying datasource:

Here is example:

Code:

---

@RowMapperObjectField(
        provideViaSqlProvider =
                @RowMapperSqlProvider(
                        sql =
                                "SELECT r.* FROM ROLE r WHERE r.ID IN " +
                                "(" +
                                        "SELECT ur.ROLE_ID FROM user_role ur WHERE ur.USER_ID = ${id}" +
                                ") ORDER BY r.name",
                        dataSource = "MyDataSource"),
                lazy = true)

---

3. Binding results sets to object as asynchronous.
My new JdbcTemplate will return proxy objects immediately without binding resultsets to objects.
At backend, worker threads run for binding resultsets to objects.
If an unbinded object is accessed, thread, tried to access, will be suspended until resultset binded to object.

Cheers,

--

Serkan ÖZAL