Fix cleanUpExpiredSessions operation in JdbcOperationsSessionRepository

[vpavic]

Currently, JdbcOperationsSessionRepository#cleanUpExpiredSessions only considers the repository defined max inactive interval which causes incorrect cleanup of sessions that define custom inactive interval. This commit fixes the problem by delegating calculation of deletion interval to the underlying SQL DELETE statement.

Additionally, due to shortcomings in H2 and Derby databases which make them incompatible with newly introduced DELETE statement, the setters for customizing SQL queries have been also added.

This resolves #580 and #609.

[rwinch]

Thanks for the PR @vpavic!

You can use a single PR, but can you please split the commits into two distinct commits for the specific issues?

I'm wondering if we can improve this slightly so that the JdbcHttpSessionConfiguration detects the Database vendor and updates the query for H2 and Derby using something like:

@Bean
public JdbcOperationsSessionRepository sessionRepository(
        @Qualifier("springSessionJdbcOperations") JdbcTemplate jdbc,
        PlatformTransactionManager transactionManager) throws Exception {
    String vendor = jdbc.getDataSource().getConnection().getMetaData().getDatabaseProductName();
    boolean isH2 = "h2".equalsIgnoreCase(vendor);
        ...

Thoughts?

[vpavic]

You can use a single PR, but can you please split the commits into two distinct commits for the specific issues?

Done.

I'm wondering if we can improve this slightly so that the JdbcHttpSessionConfiguration detects the Database vendor and updates the query for H2 and Derby

I like the idea. Done as well with the latest PR update.

[rwinch]

Thanks for the PR! This is now merged into master