The comments to this StackOverflow question (http://stackoverflow.com/questions/10667292/jdbc-check-for-capability-savepoint-release) seems to suggest that this might not work, but I'll give it a go...

On Wed, Jul 24, 2013 at 7:50 PM, Yavor Nikolov <notifications@github.com>
wrote:

>> @@ -211,5 +211,13 @@ public static void checkConnectionValid(final Connection conn)
>>          }
>>      }
>>  
>> +    public StatementExecutionFeatures getStatementExecutionFeatures() {
>> +        return new StatementExecutionFeatures() {
>> +            @Override
>> +            public boolean supportsSavepointReleasing() {
> In theory seems this can be implemented by checking if <a href="http://docs.oracle.com/javase/7/docs/api/java/sql/Connection.html#releaseSavepoint(java.sql.Savepoint)">releaseSavepoint throws SQLFeatureNotSupportedException</a>. Maybe a bit ugly but should avoid the need of up-front knowledge of driver behaviour (which may vary per version).
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/benilovj/dbfit/pull/150/files#r5380287